Re: Mandatory Changelogs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, 27 Oct 2007 at 18:55:34 -0400, Michael Stone wrote: Dear Sugar and Devel, ChangeLogs in the format described on http://wiki.laptop.org/go/Build_system#ChangeLog_Format are now MANDATORY for package inclusion. Please write yours. How does this work for Koji users? I build the OLPC Telepathy components for what-was-FRS-last-time-I-looked in the OLPC-2 stream in Koji. Will they be integrated into Joyride automatically, or do I have to download the RPMs (assuming that's even possible) and re-upload them via my public_rpms? If they're integrated automatically, how and where do I write changelogs? I'm happy to write the RPM %changelog in the desired format if that's what you want... Simon -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: OpenPGP key: http://www.pseudorandom.co.uk/2003/contact/ or pgp.net iD8DBQFHJbPmWSc8zVUw7HYRAu7uAJ48urtIwmlI4/MMSsgxNBYD7OAcEgCfbwp3 vj+9tWFehBxQ7azm1xJYYFk= =BF29 -END PGP SIGNATURE- ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Mandatory Changelogs
Simon, Thanks for your question. The short answer is that Koji and the dropboxes are completely independent, parallel mechanisms for creating binary RPM repositories to be composed by pilgrim into a build image. Today, ChangeLogs are required only for packages included by the dropbox mechanism. We are in discussions with folks who are knowledgable about Koji (namely Dave Woodhouse and Dennis Gilmore) to produce a wrapper for the Koji tag command that will record similar information. In the meantime, writing detailed RPM changelogs that describe the purpose of introducing the new package (in addition to any packaging changes) would be enourmously useful. Checking the source: http://dev.laptop.org/git?p=users/cscott/pilgrim;a=blob;f=streams.d/olpc-development-yum-install.conf;hb=joyride shows that Joyride is indeed configured to pull packages from the OLPC-2 Koji collection. Best, Michael On Mon, Oct 29, 2007 at 10:20:22AM +, Simon McVittie wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, 27 Oct 2007 at 18:55:34 -0400, Michael Stone wrote: Dear Sugar and Devel, ChangeLogs in the format described on http://wiki.laptop.org/go/Build_system#ChangeLog_Format are now MANDATORY for package inclusion. Please write yours. How does this work for Koji users? I build the OLPC Telepathy components for what-was-FRS-last-time-I-looked in the OLPC-2 stream in Koji. Will they be integrated into Joyride automatically, or do I have to download the RPMs (assuming that's even possible) and re-upload them via my public_rpms? If they're integrated automatically, how and where do I write changelogs? I'm happy to write the RPM %changelog in the desired format if that's what you want... Simon -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: OpenPGP key: http://www.pseudorandom.co.uk/2003/contact/ or pgp.net iD8DBQFHJbPmWSc8zVUw7HYRAu7uAJ48urtIwmlI4/MMSsgxNBYD7OAcEgCfbwp3 vj+9tWFehBxQ7azm1xJYYFk= =BF29 -END PGP SIGNATURE- ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Mandatory Changelogs
On Sat, 27 Oct 2007 18:55:34 -0400 Michael Stone [EMAIL PROTECTED] wrote: Dear Sugar and Devel, ChangeLogs in the format described on http://wiki.laptop.org/go/Build_system#ChangeLog_Format are now MANDATORY for package inclusion. Please write yours. Ok, I have a *serious* problem with this. First of all, this is the first I've heard of requiring changelogs. Second, making them mandatory immediately (the Build_system wiki page was created yesterday?) doesn't give people time to update scripts they might have. Kernel packages are not done manually; they are autobuilt. I don't know which ones make it into which builds. I don't have time right now to update my build scripts. Sure, I think changelogs are a great idea, and I'm more than happy to update the kernel build scripts to generate them, but I've got more important bugs to fix right now for the Nov 2 deadline. Special thanks to Bert Freudenberg (bertf) and Marc Maurer (uwog) for setting a great example! Let me know if you have any trouble. Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Mandatory Changelogs
I think Michael over stated the request. We'd like Changelogs, the sooner, the better, when new things to into the builds. This is so we can better test what's being changed, and have a better clue about what might break. Often this can be generated from version control system comments, even automatically. But we're interested in a higher level view of what is going on than these would generate. For example, putting in the X 1.4 packages, if one generated a change log from git for all of that, we'd be lost in hundreds/thousands of log entries that that major update implies. The forest would be lost for the trees. Describing that those packages are to update to use to the new input system and pick up better graphics support, and fix trac #1234 that was causing so much grief is the high level overview we're asking for here. This can give people the idea that they should test input carefully, and if something funny changes on the screen, maybe X is at fault, rather than their activity. If they need more detail, then If we can agree on a common format, then we can automate the roll up into a build message. Regards, - Jim We'd like people to look at the described format On Sat, 2007-10-27 at 18:55 -0400, Michael Stone wrote: Dear Sugar and Devel, ChangeLogs in the format described on http://wiki.laptop.org/go/Build_system#ChangeLog_Format are now MANDATORY for package inclusion. Please write yours. Special thanks to Bert Freudenberg (bertf) and Marc Maurer (uwog) for setting a great example! Let me know if you have any trouble. Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Jim Gettys One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
