Mailinglist Archive: opensuse-factory (988 mails)

< Previous Next >
Re: [opensuse-factory] New Tumbleweed snapshot 20150630 released!
  • From: Brüns, Stefan <Stefan.Bruens@xxxxxxxxxxxxxx>
  • Date: Fri, 3 Jul 2015 15:42:02 +0000
  • Message-id: <5158410.0ULnciVVsk@sbruens-linux>
On Friday, July 03, 2015 16:39:22 you wrote:
On Fri, Jul 03, 2015 at 05:38:25PM +0300, Andrei Borzenkov wrote:
On Fri, Jul 3, 2015 at 5:30 PM, Brüns, Stefan

<Stefan.Bruens@xxxxxxxxxxxxxx> wrote:
On Friday, July 03, 2015 06:47:24 Marcus Meissner wrote:
On Fri, Jul 03, 2015 at 12:07:42AM +0300, Andrei Dziahel wrote:
Hi list,

Great to see next snapshot, but it comes with a problem — is it is
huge which may be the burden for users with less performant internet
connection (say I've got 2.2G to download on primary desktop and 1.5G
on secondary desktop/fileserver).

Can delta rpm building and publishing be enabled for Tumbleweed
repositories? That would save not just bandwidth but also time of
fellow Tumbleweed enthusiasts. Or, if there's concerns of any sort,
make it opt-in so project owners could test-drive it before enabling
it globally.

You probably saw that usually the changes are small.

As we changed the system compiler, all packages had to be rebuilt.
delta rpms would not have made it significantly smaller, as a new
major compiler version usually changes a lot of things.

Ciao, Marcus

By their very nature, noarch packages wont be affected by a compiler
change.

Often, these are large packages (wallpapers, documentation with
screenshots).

Often, the package contents do not change even for newer versions.

Please correct, if I am wrong.

The content of such package may still be generated at build time (like
genrating font from some source format) and tool to do it may need to
be compiled. In this case package probably has BuildRequires on gcc
which will trigger rebuild (I think).

We cover a lot of unchanging packages using build-compare. If build-compare
worked, the package would not get updated in a full rebuild scenario.

build-compare decides on the source rpm level, IIRC. If one spec/source-rpm
generates arch dependent and noarch packages, the noarch will also be
published even if only the arch dependent packages has changed.

This is common for doc and lang packages, and even some wallpaper packages,
e.g. KF5:breeze5.

There is also the case (not related to the mass rebuild) when only the
changelog is updated. This would be covered by a delta rpm, but of course
registers as a package change with build-compare.

Regards,

Stefan

--
Stefan Brüns / Bergstraße 21 / 52062 Aachen
home: +49 241 53809034 mobile: +49 151 50412019
work: +49 2405 49936-424
< Previous Next >