The attachment should have generated a response over two hours ago, right? I don't
see anything. Is something about subscription management known broken?
A recent/subsequent attempt to do same generated a waiting on moderator message.
Then I switched the "To" from ...(a)opensuse.org to ...(a)lists.opensuse.org and tried
again. That was over half an hour ago, and still no response.
Currently reporting a database error - just wanted to ensure that the
Heroes team was aware of the outage.
--
Jim Henderson
Please keep on-topic replies on the list so everyone benefits
Hi Mark,
Thanks for stepping up for election, I will be writing to you officially
on the project page very soon.
Unfortunately as election officials we don't (rightly so) have anything
to do with opensuse.org email cloaks etc. Looks like something somewhere
along the line has gone wrong. You are obviously still on the project as
you successfully posted on the lists, and I can also find your profile
at https://connect.opensuse.org/pg/profile/m4r3k
I am copying this to and also to mstopka(a)opensuse.org to see what
happens, as well as heroes(a)opensuse.org they are the guys who will be
able to help sort this out. Heroes, please work with Mark to get this
sorted out.
Cheers,
Ariez
ajv(a)opensuse.org
On 16/11/2020 00:54, Mark Stopka wrote:
> Hi Ariez, I've sent my application from at that time non-subscribed
> e-mail address and it is pending approval, do you think you could do
> something about it?
>
> Thanks in advance, somehow, when I joined the project @opensuse.org
> <http://opensuse.org> addresses were not a thing :-)
> --
> Best regards / S pozdravem,
> BSc. Mark Stopka, BBA
>
> mobile: +420 704 373 561
>
>
> On Sun, Nov 15, 2020 at 11:54 AM Ariez Vachha - openSUSE
> <AJV(a)opensuse.org <mailto:AJV@opensuse.org>> wrote:
>
> Dear openSUSE members,
>
> openSUSE Board Election 2020 [1]
>
> It's time to elect new Board members to fill empty seats on the
> openSUSE Board. This is a regular election as defined in our
> Election Rules [2] so the elected board members will serve till the
> end of 2022.
>
> There are three seats for election in accordance with our normal
> election cycle. Stasiek is opting not to continue for the next full
> year due to a change in his personal circumstances.
>
> The election schedule is as follows:
>
> ## Phase 0
>
> 15 November 2020
> - Announcement of the openSUSE Board Election 2020
> - Call for Nominations and Applications for Board candidacy
> Membership drive
>
> 29 November 2020
> - Nominations and Applications for Board candidacy close
>
> ## Phase 1
>
> 30 November 2020
> - Announcement of the final list of candidates
> - Campaign begins
> - Membership drive continues, opportunity to apply for openSUSE
> Membership, but members will only be eligible to vote and not run
> as a candidate
>
> ## Phase 2
>
> 15 December 2020
> - Ballots open: Please cast your vote during this time
> - Campaign continues
>
> 30 December 2020
> - Ballots close
>
> 31 December 2020
> - Announcement of results
>
> To stand for a position in the openSUSE Board please send an email to:
>
> * opensuse-project(a)opensuse.org
> <mailto:opensuse-project@opensuse.org> and
> * election-officials(a)opensuse.org
> <mailto:election-officials@opensuse.org>
>
> If a member would like to nominate another member, please inform the
> Election Committee and the officials will contact the nominee to ask
> whether they would like to run as a Board candidate.
>
> Only openSUSE members are eligible to run for openSUSE Board openings in
> accordance with the Eligibility and Validity section of our Election
> Rules [2].
>
> The Election Committee [3] are hereby calling for Nominations &
> Applications for the openSUSE Board.
>
>
> [1] https://en.opensuse.org/openSUSE:Board_election
> <https://en.opensuse.org/openSUSE:Board_election>
> [2] https://en.opensuse.org/openSUSE:Board_election_rules
> <https://en.opensuse.org/openSUSE:Board_election_rules>
> [3] Members: Ish Sookun, Edwin Zakaria and Ariez Vachha.
>
> --
> Regards,
> The Election Committee election-officials(a)opensuse.org
> <mailto:election-officials@opensuse.org>
> _______________________________________________
> openSUSE Project mailing list -- project(a)lists.opensuse.org
> <mailto:project@lists.opensuse.org>
> To unsubscribe, email project-leave(a)lists.opensuse.org
> <mailto:project-leave@lists.opensuse.org>
> List Netiquette:
> https://en.opensuse.org/openSUSE:Mailing_list_netiquette
> <https://en.opensuse.org/openSUSE:Mailing_list_netiquette>
> List Archives:
> https://lists.opensuse.org/archives/list/project@lists.opensuse.org
> <https://lists.opensuse.org/archives/list/project@lists.opensuse.org>
>
Hi all,
Could you please make these two emails addresses, tweet-os(a)opensuse.org
and shop(a)opensuse.org, to help with continuity for the project and list
me, henne and vinz(a)vinzv.de to receive these emails. They are associated
with some social media accounts and our shop. The migration must have
deleted these accounts as the tests don't work.
v/r
Doug
Hi all,
As part of improvements to download.opensuse.org experience, currently new pilot service is available for using with zypper.
https://mirrorcache.opensuse.org
Its primary task is to redirect zypper requests to a mirror in client's country, similar to what MirrorBrain project does.
You can try to replace in /etc/zypp/repos.d/*.repo
http://download.opensuse.org
with
http://mirrorcache.opensuse.org
or
https://mirrorcache.opensuse.org
Since it is still a pilot, the service comes without any guarantee or obligations.
Reasons when you may want to try it:
- you want to stick to https connection (mirrorcache will try to find a mirror in your country, which supports https, if available).
- you are on ipv4-only or ipv6-only connection (mirrorcache will try to find a mirror which supports ipv4 or ipv6, depending on the request's connection);
- in case when download.opensuse.org (d.o.o) is temporary unavailable;
- redirection from d.o.o leads to a mirror, which actually doesn't have the requested file (it is rare, but can happen);
- you want to try hosting own mirrorcache instance at your physical location and enjoy fast and reliable redirection. (with very modest disk space / HW requirements).
Additional reasons:
- you want to help with improving d.o.o experience and provide feedback;
- you are interested in mirror management, for which admin's UI is available, and non-admin UI is planned (so a user can add and manage own mirror without global admin rights);
https://mirrorcache.opensuse.org/app/server
(login using UI menu and ask me for admin rights if you want to use it or see more advanced controls, like job details).
- you need some related functionality: it is possible that it can be easily achievable with mirrorcache.
Further read about differences from MirrorBrain:
https://github.com/andrii-suse/MirrorCache/blob/master/doc/mb_compare.md
How caching works:
- caching happens on folder level, so e.g., when zypper tries to access file, unknown for mirrorcache - it will be redirected to d.o.o, then a background job will collect info about mirrors. Thereafter further requests to the same folder will be properly redirected to a mirror in the client's country, honoring http/https scheme and ipv4/ipv6 connection used:
https://raw.githubusercontent.com/andrii-suse/MirrorCache/master/doc/flow.s…
- requests to remodata/repomd.xml is not cached, so zypper always gets the latest version of packages.
If you are interested in current source code
(most of architecture is stolen from OpenQA):
https://github.com/andrii-suse/MirrorCache
In case of questions or any feedback do not hesitate to contact me.
Regards,
--
Andrii Nikitin <andrii.nikitin(a)suse.com>
DevOPS Automation and Build Service Engineer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5
90409 Nuremberg
Germany
(HRB 247165, AG München)
Managing Director: Felix Imendörffer
Hi all,
On 11/12/20 4:55 PM, Witek Bedyk wrote:
> Hi Doug,
>
> could you please take a look at this PR?
>
> https://github.com/openSUSE/openSUSE-release-tools/pull/2493
>
> After updating the packages the script should aggregate the data for
> Leap 15.2 as well.
>
> Cheers
> Witek
>
Witek provided a commit for Leap 15.2 to be shown on
https://metrics.opensuse.org/. I merged and felt that it would trigger
the data to be processed, which could take some time like it says at the
bottom of
https://github.com/openSUSE/openSUSE-release-tools/tree/master/metrics/acce…
From what I read, it looks like the merge should work.
The documentation did state that the archival log data is located on a
different network from the active data and the tool must be run from a
machine with access to both or in two steps.
I'm not sure what this means or if the machine needs to be triggered to
see the results. The other products link 15.0 and 15.2 are still being
parsed. I don't think it is a hardware issue as it's just processing the
data, which could take some time for the new data. So far metrics.o.o
has not updated the statistics to reflect Leap 15.2.
v/r
Doug
Is there any particular need for [whatever] in list subject lines to be followed
by two spaces instead of one? It breaks alphabetic listing of/by subject lines.
--
Evolution as taught in public schools, like religion,
is based on faith, not on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
-------- Forwarded Message --------
Subject: Undelivered Mail Returned to Sender
Date: Wed, 11 Nov 2020 04:09:27 +0000 (UTC)
From: Mail Delivery System <MAILER-DAEMON(a)suse.de>
To: sflees(a)suse.de
This is the mail system at host relay2.suse.de.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The mail system
<project(a)lists.opensuse.org>: host 127.0.0.1[127.0.0.1] said: 554 5.4.0
id=02257-03-3 - Rejected by next-hop MTA on relaying, from
MTA(smtp:[127.0.0.1]:25): 554 5.4.0 Error: too many hops (in reply
to end
of DATA command)
On Tue 2020-11-10, Witek Bedyk wrote:
> updating the tool to track Leap 15.2 is simple. It's just updating the
> regex for product pattern to match.
> I can take care of it. It's actually one of few documented items [1].
Cool, thank you!
> My work was focused on extending the collected information and storing
> statistics about package downloads. Meaning, how often a given package
> gets downloaded on a day, week, month.
> The problem is that the script in current shape caches a lot of data on
> the disk which fills up already. I've written a short summary of that
> here [2]. I've done some work already to redesign the script and move
> the aggregation part from cache files into InfluxDB.
>
> [2] https://progress.opensuse.org/issues/69535#note-1
How much effort do you think this will be (roughly), and do
you have a (again rough) ETA?
If it takes longer, and some investment (like a disk or two)
does make a difference, can you please advise and I hope we
can get that quickly (either via eng-infra/management, or if
I have to chat with Thomas DiG I'll do that, too).
Thank you,
Gerald
Hi,
After a few months of preparation we will be switching mailing lists
over to Mailman on 10. November. The current plan is as follows:
1. 9. Nov 10:00 CET E-Mail sent out to all of the current subscribers of
all of our mailing lists to notify them of downtime the following day
2. 10. Nov 10:00 CET Mailing Lists are frozen and LCP runs all of the
migration scripts ;)
3. When the mailing lists are back up, an E-Mail is sent out to all of
the migrated subscribers notifying them of the migration being
finished and begging them to report any bugs
I expect the mailing lists to be down only for a couple of hours, but in
case everything goes wrong, the mailing lists might only come back the
next day
There is a wiki page link to which will be included with both E-Mails
explaining the differences between mlmmj and mailman3:
https://en.opensuse.org/openSUSE:Mailing_Lists_Migration
We have already migrated:
* opensuse-test <test(a)lists.opensuse.org>
* heroes <heroes(a)lists.opensuse.org>
* uyuni-announce <announce(a)lists.uyuni-project.org>
* uyuni-devel <devel(a)lists.uyuni-project.org>
* uyuni-users <users(a)lists.uyuni-project.org>
* uyuni-translate <translate(a)lists.uyuni-project.org>
Feel free to play around with opensuse-test mailing list to test how it
works as well ;)
LCP [Stasiek]
https://lcp.world
