On 10 November 2015 at 18:07, PGNet Dev <pgnet.dev@gmail.com> wrote:
At every Opensuse release, scads of non-home repos fail to be enabled by the time of the release.
As a result, we don't upgrade until WELL AFTER release -- when, in response to our incessant nagging, all the repos finally get enabled.
And, since that's the 'real world' we operate in, we don't test the release in that 'real world' until AFTER the release.
Is that a desired project outcome?
We'd test more broadly if upgrading to a new distro didn't break stuff by forcing downgrades to our prior-distro's-non-home-repo-upgraded-packages.
Easily solved by having those equivalent repos enabled for new distro asap ...
If a devel repo has a >50% probability of being enabled eventually, it should be enabled @ release.
Perhaps it'd be useful for release mgmt to create a script that goes over all devel repos and submits an SR for enabling the new repository for the new release.
My bog-simple, after-the-fact script to find which repos' maintainers to nag is:
cat test_urls.sh #!/bin/bash URLS=`grep ^baseurl *\.repo | cut -d"=" -f2` for u in $URLS do status=$(curl -s --head -w %{http_code} $u -o /dev/null) echo $status " @ $u"
Each repo that returns a 404
sh test_urls.sh | grep 404
gets a ping/request.
I have a better solution Stop keeping stuff in home: repos! If you want stuff in the main distributions, then get it out of a home: repo and into a devel: repo and then into Tumbleweed and Leap And then this problem goes away, and everyone benefits -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org