New/updated packages take for ever to get published.

Does anyone have information/comment/solution? I’m stuck, waiting for repos to be created, refering to packages that are not available yet and unable to run installation scripts (that require adding repo and installing packages from them). How come it takes so long to publish packages after they built successfully? I keep seing the clock icon (“Build jobs have been processed, new repository is not yet created”) for hours, maybe even days. :frowning:

So I edited your title to be correct. And, I don’t know why it takes so long, but perhaps due to the many server changes that have been going on around here. And Not really sure when it is supposed to get better either.

Thank You,

On 01/22/2012 08:56 PM, jdmcdaniel3 wrote:
> So I edited your title to be correct.

‘forever’ vs ‘for ever’ or something other?


DD
openSUSE®, the “German Engineered Automobiles” of operating systems!

“forever”, at least “forme”! :wink:
But it’s a problem though.

please_try_again: There is a huge backlog in publishing packages due to the recent disk failure. This will normalize over time, where time is measured in days.

So it means that some day, it will be back to normal? They didn’t move the servers in a garage because … how should I know? …because of things that we’re not supposed to know.

Thanks for the information vodoo and very good to see you around. Here is a link about a failure, is this the one to which you refer?

The SAN array of the backend server server lost 3 hard disks over the weekend. January 14th, 2012 by Lars Vogdt


Thank You,

I chose the wrong moment to add a repo for Fedora 16. If I had known that earlier, I wouldn’t have built packages.

Thanks for the information vodoo and very good to see you around. Here is a link about a failure, is this the one to which you refer?

openSUSE News January 14th, 2012 by Lars Vogdt

Hi James

Yes. This was the incident. Interesting enough, essential hardware often fails on weekends. Apparently there was no backup of the published repositories. The publisher had to re-create all of them and this caused some backlog. The topic in the #opensuse-buildservice IRC channel still says: “Huge publishing backlog atm”. Thanks for the coffee.

On 01/27/2012 08:26 AM, vodoo wrote:
> Apparently there was no backup of the published repositories.

simply amazing! i wonder if they had hired a new graduate from one of
those IT schools that knows and teaches nothing but M$ Server??


DD
Read about openSUSE

Am 27.01.2012 10:37, schrieb DenverD:
> simply amazing! i wonder if they had hired a new graduate from one of
> those IT schools that knows and teaches nothing but M$ Server??
>
Reminds me when a biochemistry lab which is one of our customers deleted
by accident a part of our database and we told them to to recover from
the latest backup - silence for a minute on the phone. Then they told us
they do not do backups because they use RAID.


PC: oS 11.4 (dual boot 12.1) 64 bit | Intel Core i7-2600@3.40GHz | KDE
4.6.0 | GeForce GT 420 | 16GB Ram
Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.8.0 |
nVidia ION | 3GB Ram

On 01/27/2012 12:19 PM, Martin Helm wrote:
> they told us they do not do backups because they use RAID.

there are Millions and Millions who think RAID is a viable alternative
for a backup…mostly due to box maker advertising, i guess…


DD
Read about openSUSE

I was trying to utter no criticism in my post #9 because I know that these guys managing obs are true professionals who know what they are doing. The publisher module is a complex beast, taking care of signing and calculating checksums and steering the links to the web interface. The whole thing is not as easy as just playing back some backup. There was probably some very good reason to recreate all published repos from the original built packages. I am guessing here, but I trust the people who know better.

Am 27.01.2012 12:37, schrieb DenverD:
> On 01/27/2012 12:19 PM, Martin Helm wrote:
>> they told us they do not do backups because they use RAID.
>
> there are Millions and Millions who think RAID is a viable alternative
> for a backup…mostly due to box maker advertising, i guess…
>
It is sad how advertising replaces common sense even when it comes to
professionals working on expensive systems.


PC: oS 11.4 (dual boot 12.1) 64 bit | Intel Core i7-2600@3.40GHz | KDE
4.6.0 | GeForce GT 420 | 16GB Ram
Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.8.0 |
nVidia ION | 3GB Ram

Am 27.01.2012 13:06, schrieb vodoo:
> The whole thing is not as easy as just playing back some backup.
> There was probably some very good reason to recreate all published
> repos from the original built packages. I am guessing here, but I
> trust the people who know better.
>
Please also note that I am just joking a bit about the situation. I can
imagine why someone does no backup on things which are produced by a
build system, since it is probably easier to rebuild than to recover the
end product of the build from a backup as long as the source and build
system is properly backuped.


PC: oS 11.4 (dual boot 12.1) 64 bit | Intel Core i7-2600@3.40GHz | KDE
4.6.0 | GeForce GT 420 | 16GB Ram
Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.8.0 |
nVidia ION | 3GB Ram

On 01/27/2012 01:16 PM, Martin Helm wrote:
> produced by a build system

hmmmmmm…and, i now admit i’d not actually thought about the scope or
‘value’ of data involved… hmmmmmmmmmmm


DD
Read about openSUSE