https://bugzilla.novell.com/show_bug.cgi?id=699269 https://bugzilla.novell.com/show_bug.cgi?id=699269#c0 Summary: Build service repositories should keep not-only newest versions of packages - breaks installs Classification: Internal Novell Products Product: openSUSE Build Service Version: 2.3 Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: source services AssignedTo: adrian@novell.com ReportedBy: llipavsky@novell.com QAContact: adrian@novell.com CC: dcollingridge@novell.com, chrubis@novell.com, vmarsik@novell.com, cachen@novell.com, llwang@novell.com, aguo@novell.com, jtang@novell.com, dmulder@novell.com Found By: --- Blocker: --- Found in version: current on build suse.de (I am not sure whether it is really 2.3) Currently, build service repository (at least in internal build service) keeps only the most recent versions of packages build. This causes a real problem, when new package is build during the system installation which has added the BS repository. The installation at its first phase construct the list of packages to install and than the installation begins. If newer package is built during the installation, the installation reports an error "unable to find package XXX-VERSION" since there is only a newer version in the repository. This makes our QA Automated installations to fail (or worse, the intallation after some time completes ignoring the error, but our automation tools do not work, system does not show in our controllers, etc.) Would it be possible to delete packages after some timeout, and not immediatelly when the next version is available - somthing like 2 hours hsould be enough? This cannot be simple workarounded by keeping (e.g.) last two versions, since it often happens that we submit multiple times to BS during several minutes (found a bug & sfubmit bugfix, more developers working on same package, etc.) Thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.