[opensuse-kernel] RFC: Use tarballs for -rc and stable releases?
Hi, currently, -rc and stable release updates are done by adding patches to patches.kernel.org/. Especially the -rc1 patches are *huge* and cannot be paired with any other object in the repository, so their gzip-compressed size adds to the total repository size: $ git cat-file -p b9044e3353ff21f12a86788a18cf36ba1071b6ab:patches.kernel.org/patch-2.6.37-rc1 | gzip -c -9 | wc -c 14627847 that is almost 14 megabytes. So I would like to propose to more or less discontinue patches.kernel.org and instead use the SRCVERSION variable in rpm/config.sh. This is already used in the vanilla and linux-next branches and it works. Code changes are more easily reviewed in the kernel.git nowadays, tar-up.sh and sequence-patch also work if you don't have the tarball around (it generates one from git, which is arguably slower, but works), so I think it's worth doing it. Opinions? Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/31/2011 10:32 AM, Michal Marek wrote:
Hi,
currently, -rc and stable release updates are done by adding patches to patches.kernel.org/. Especially the -rc1 patches are *huge* and cannot be paired with any other object in the repository, so their gzip-compressed size adds to the total repository size: $ git cat-file -p b9044e3353ff21f12a86788a18cf36ba1071b6ab:patches.kernel.org/patch-2.6.37-rc1 | gzip -c -9 | wc -c 14627847
that is almost 14 megabytes. So I would like to propose to more or less discontinue patches.kernel.org and instead use the SRCVERSION variable in rpm/config.sh. This is already used in the vanilla and linux-next branches and it works. Code changes are more easily reviewed in the kernel.git nowadays, tar-up.sh and sequence-patch also work if you don't have the tarball around (it generates one from git, which is arguably slower, but works), so I think it's worth doing it.
I like the idea. We don't ever modify those patches -- if we did, we're doing something wrong. The down side is that replacing the entire tarball means that the OBS project gets a new tarball every time we do an -rc or -stable bump. That's time consuming when syncing the project. If we could work it so that it uses the incremental patches, that would be perfect. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk2UlXsACgkQLPWxlyuTD7IyTwCbBES6BbTUcg4KL3PGqygbf4dt 6O8An0nEdqu46T+hEeIHSbHUddF64T9t =Sgxi -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On 31.3.2011 16:53, Jeff Mahoney wrote:
I like the idea. We don't ever modify those patches -- if we did, we're doing something wrong.
Great.
The down side is that replacing the entire tarball means that the OBS project gets a new tarball every time we do an -rc or -stable bump.
Hm, right, I didn't think of that.
That's time consuming when syncing the project. If we could work it so that it uses the incremental patches, that would be perfect.
Automatically generating incremental patches would be tricky (and also too much script bloat for a relatively little gain...). But it should be possible to eliminate uploading the upstream tarball completely if we can use "source services": http://doc.opensuse.org/products/draft/OBS/obs-reference-guide_draft/cha.obs... . As far as I understand, it is possible to upload a small xml file instead that contains the url of the tarball to download. Anyway, could you try the tarball method when you update to 2.6.39-rcX? A couple of more linux tarballs will surely not kill the buildservice. I'll look into the source service thing in parallel. Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/31/2011 03:32 PM, Michal Marek wrote:
On 31.3.2011 16:53, Jeff Mahoney wrote:
I like the idea. We don't ever modify those patches -- if we did, we're doing something wrong.
Great.
The down side is that replacing the entire tarball means that the OBS project gets a new tarball every time we do an -rc or -stable bump.
Hm, right, I didn't think of that.
That's time consuming when syncing the project. If we could work it so that it uses the incremental patches, that would be perfect.
Automatically generating incremental patches would be tricky (and also too much script bloat for a relatively little gain...). But it should be possible to eliminate uploading the upstream tarball completely if we can use "source services":
No, I don't mean we generate our own. That would be a big pain. Our patch-2.6.xx-rcy patches aren't generated by us. Upstream does that already. They're from ftp://ftp.kernel.org/pub/linux/kernel/v2.6/testing/incr/
http://doc.opensuse.org/products/draft/OBS/obs-reference-guide_draft/cha.obs... . As far as I understand, it is possible to upload a small xml file instead that contains the url of the tarball to download.
Anyway, could you try the tarball method when you update to 2.6.39-rcX? A couple of more linux tarballs will surely not kill the buildservice. I'll look into the source service thing in parallel.
Sure. That'll work with mbuild for now too, right? It picks up whatever we throw in that variable. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk2VS3MACgkQLPWxlyuTD7LFvQCfZb0z9RIMBvLzrWIA9MuI0GBY A98An1T1obewDdGhfeNMg3OsYa4GYxxz =CGiO -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/31/2011 11:50 PM, Jeff Mahoney wrote:
On 03/31/2011 03:32 PM, Michal Marek wrote:
On 31.3.2011 16:53, Jeff Mahoney wrote:
I like the idea. We don't ever modify those patches -- if we did, we're doing something wrong.
Great.
The down side is that replacing the entire tarball means that the OBS project gets a new tarball every time we do an -rc or -stable bump.
Hm, right, I didn't think of that.
That's time consuming when syncing the project. If we could work it so that it uses the incremental patches, that would be perfect.
Automatically generating incremental patches would be tricky (and also too much script bloat for a relatively little gain...). But it should be possible to eliminate uploading the upstream tarball completely if we can use "source services":
No, I don't mean we generate our own. That would be a big pain. Our patch-2.6.xx-rcy patches aren't generated by us. Upstream does that already. They're from ftp://ftp.kernel.org/pub/linux/kernel/v2.6/testing/incr/
Oh, and the rcy-gitz patches are incrementally updated at ftp://ftp.kernel.org/pub/linux/kernel/v2.6/snapshots/incr/ as well. - -Jeff
http://doc.opensuse.org/products/draft/OBS/obs-reference-guide_draft/cha.obs... . As far as I understand, it is possible to upload a small xml file instead that contains the url of the tarball to download.
Anyway, could you try the tarball method when you update to 2.6.39-rcX? A couple of more linux tarballs will surely not kill the buildservice. I'll look into the source service thing in parallel.
Sure. That'll work with mbuild for now too, right? It picks up whatever we throw in that variable.
-Jeff
- -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk2VS7YACgkQLPWxlyuTD7KzGwCeNIBh6gO8NDNwmhoy0F9oVc5X yq4An18cX1ZhuI6sH8BpXjNG19mfnb9X =D3Rj -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/31/2011 11:51 PM, Jeff Mahoney wrote:
On 03/31/2011 11:50 PM, Jeff Mahoney wrote:
On 03/31/2011 03:32 PM, Michal Marek wrote:
On 31.3.2011 16:53, Jeff Mahoney wrote:
I like the idea. We don't ever modify those patches -- if we did, we're doing something wrong.
Great.
The down side is that replacing the entire tarball means that the OBS project gets a new tarball every time we do an -rc or -stable bump.
Hm, right, I didn't think of that.
That's time consuming when syncing the project. If we could work it so that it uses the incremental patches, that would be perfect.
Automatically generating incremental patches would be tricky (and also too much script bloat for a relatively little gain...). But it should be possible to eliminate uploading the upstream tarball completely if we can use "source services":
No, I don't mean we generate our own. That would be a big pain. Our patch-2.6.xx-rcy patches aren't generated by us. Upstream does that already. They're from ftp://ftp.kernel.org/pub/linux/kernel/v2.6/testing/incr/
Oh, and the rcy-gitz patches are incrementally updated at ftp://ftp.kernel.org/pub/linux/kernel/v2.6/snapshots/incr/ as well.
Hi Michal - I don't suppose you've made any progress here? I'd like to rev the master kernel to 2.6.39-rc2, but if you've got something working here, I'll wait to do that. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk2jcDYACgkQLPWxlyuTD7JcMwCghakxE3TPpFoZb3I8WS3/eGZp fIMAn2jNP05K6X9a7x3iFF/Upmi+vrHs =RM5A -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On 11.4.2011 23:18, Jeff Mahoney wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/31/2011 11:51 PM, Jeff Mahoney wrote:
On 03/31/2011 11:50 PM, Jeff Mahoney wrote:
On 03/31/2011 03:32 PM, Michal Marek wrote:
On 31.3.2011 16:53, Jeff Mahoney wrote:
I like the idea. We don't ever modify those patches -- if we did, we're doing something wrong.
Great.
The down side is that replacing the entire tarball means that the OBS project gets a new tarball every time we do an -rc or -stable bump.
Hm, right, I didn't think of that.
That's time consuming when syncing the project. If we could work it so that it uses the incremental patches, that would be perfect.
Automatically generating incremental patches would be tricky (and also too much script bloat for a relatively little gain...). But it should be possible to eliminate uploading the upstream tarball completely if we can use "source services":
No, I don't mean we generate our own. That would be a big pain. Our patch-2.6.xx-rcy patches aren't generated by us. Upstream does that already. They're from ftp://ftp.kernel.org/pub/linux/kernel/v2.6/testing/incr/
Oh, and the rcy-gitz patches are incrementally updated at ftp://ftp.kernel.org/pub/linux/kernel/v2.6/snapshots/incr/ as well.
Hi Michal -
I don't suppose you've made any progress here? I'd like to rev the master kernel to 2.6.39-rc2, but if you've got something working here, I'll wait to do that.
- -Jeff
Not yet, sorry. Try setting SRCVERSION=2.6.39-rc2 in rpm/config.sh, that should work for now. Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/12/2011 05:03 AM, Michal Marek wrote:
On 11.4.2011 23:18, Jeff Mahoney wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/31/2011 11:51 PM, Jeff Mahoney wrote:
On 03/31/2011 11:50 PM, Jeff Mahoney wrote:
On 03/31/2011 03:32 PM, Michal Marek wrote:
On 31.3.2011 16:53, Jeff Mahoney wrote:
I like the idea. We don't ever modify those patches -- if we did, we're doing something wrong.
Great.
The down side is that replacing the entire tarball means that the OBS project gets a new tarball every time we do an -rc or -stable bump.
Hm, right, I didn't think of that.
That's time consuming when syncing the project. If we could work it so that it uses the incremental patches, that would be perfect.
Automatically generating incremental patches would be tricky (and also too much script bloat for a relatively little gain...). But it should be possible to eliminate uploading the upstream tarball completely if we can use "source services":
No, I don't mean we generate our own. That would be a big pain. Our patch-2.6.xx-rcy patches aren't generated by us. Upstream does that already. They're from ftp://ftp.kernel.org/pub/linux/kernel/v2.6/testing/incr/
Oh, and the rcy-gitz patches are incrementally updated at ftp://ftp.kernel.org/pub/linux/kernel/v2.6/snapshots/incr/ as well.
Hi Michal -
I don't suppose you've made any progress here? I'd like to rev the master kernel to 2.6.39-rc2, but if you've got something working here, I'll wait to do that.
- -Jeff
Not yet, sorry. Try setting SRCVERSION=2.6.39-rc2 in rpm/config.sh, that should work for now.
This has been working perfectly. It's only a little painful having to download the tarball for each rc. It's much less painful than having to re-upload the -rc patch every time. Thanks! - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk2tp8kACgkQLPWxlyuTD7Iv1wCdF5on2SJueEeV1S2FMt9CBWD3 M+0An01RlTv7Bs9pA50+gkY/jhdCPYnQ =JOWG -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On 19.4.2011 17:18, Jeff Mahoney wrote:
On 04/12/2011 05:03 AM, Michal Marek wrote:
Not yet, sorry. Try setting SRCVERSION=2.6.39-rc2 in rpm/config.sh, that should work for now.
This has been working perfectly. It's only a little painful having to download the tarball for each rc. It's much less painful than having to re-upload the -rc patch every time.
I'm glad to hear that it works fine for you. The next step, using source services to avoid uploading the linux tarball to the buildservice, is currently waiting for an osc change to be merged: http://lists.opensuse.org/opensuse-buildservice/2011-04/msg00176.html. Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On 19.4.2011 17:51, Michal Marek wrote:
I'm glad to hear that it works fine for you. The next step, using source services to avoid uploading the linux tarball to the buildservice, is currently waiting for an osc change to be merged: http://lists.opensuse.org/opensuse-buildservice/2011-04/msg00176.html.
The current source service implementation is going to change, see http://lists.opensuse.org/opensuse-factory/2011-05/msg00037.html. So I'll stop wasting my time with this and revisit it once the implementation is stable. Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
participants (2)
-
Jeff Mahoney -
Michal Marek