Hi,
i have setup a flashrom poject at http://launchpad.net/flashrom which auto-imports the svn every 6 hours and a package archive at http://launchpad.net/~flashrom-developers/+archive/flashrom-daily where new binaries are generated once a day whenever the svn has changed.
currently there is a bug in launchpad itself that makes it impossible to use version 0.4 recipes (recipes are used to configure the autobuilders). this is the reason the package names are a bit awkward (e.g. 0.9.5.1+r1508-1-20120303 for svn r1512). it is basically named by {debversion}-{date}. it is the best i could come up with, that indicates the included source in at least some way (date), will upgrade to newer ubuntu versions when they become available and actually build in current launchpad.
another problem is that the autobuilt binaries will output this: flashrom v0.9.5.1-runknown on Linux 2.6.35-32-generic (x86_64), built with libpci 3.1.7, GCC 4.4.5, little endian i.e. no svn revision. the only way to work around this would be a second svn tree with an already (auto-)exported version of flashrom... if we could manage to set that up, we could probably build our own package too without launchpad :)
maybe it is useful anyway for someone...
Hi Stefan,
Am 04.03.2012 20:59 schrieb Stefan Tauner:
i have setup a flashrom poject at http://launchpad.net/flashrom which auto-imports the svn every 6 hours and a package archive at http://launchpad.net/~flashrom-developers/+archive/flashrom-daily where new binaries are generated once a day whenever the svn has changed.
Thanks, that's very useful.
currently there is a bug in launchpad itself that makes it impossible to use version 0.4 recipes (recipes are used to configure the autobuilders). this is the reason the package names are a bit awkward (e.g. 0.9.5.1+r1508-1-20120303 for svn r1512). it is basically named by {debversion}-{date}. it is the best i could come up with, that indicates the included source in at least some way (date), will upgrade to newer ubuntu versions when they become available and actually build in current launchpad.
another problem is that the autobuilt binaries will output this: flashrom v0.9.5.1-runknown on Linux 2.6.35-32-generic (x86_64), built with libpci 3.1.7, GCC 4.4.5, little endian i.e. no svn revision. the only way to work around this would be a second svn tree with an already (auto-)exported version of flashrom... if we could manage to set that up, we could probably build our own package too without launchpad :)
The chromium branch of flashrom has a script which can extract the svn version from git, in case that would help here. I think David even submitted it.
Regards, Carl-Daniel
On Sun, 04 Mar 2012 22:41:17 +0100 Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net wrote:
Am 04.03.2012 20:59 schrieb Stefan Tauner:
another problem is that the autobuilt binaries will output this: flashrom v0.9.5.1-runknown on Linux 2.6.35-32-generic (x86_64), built with libpci 3.1.7, GCC 4.4.5, little endian i.e. no svn revision. the only way to work around this would be a second svn tree with an already (auto-)exported version of flashrom... if we could manage to set that up, we could probably build our own package too without launchpad :)
The chromium branch of flashrom has a script which can extract the svn version from git, in case that would help here. I think David even submitted it.
well the problem is not git-related (although similar to that, because the repo launchpad syncs our svn into is not svn (but bazaar)). i can not run arbitrary commands in the recipes (possible in general, but not on launchpad due to security concerns afaik). currently i am extracting the debian directory from the ubuntu package to create the debian directory in the autobuilt ubuntu packages... maybe one could hack something into a custom made debian directory.. a quilt patch or so that extracts the svn revision. i know that the svn revision is not completely lost in bazaar because 0.4 recipes can use them for package names... OTOH i think it is good enough for now as it is. if someone wants to play around with launchpad just apply for a "flashrom-developers" membership...
Hi,
Thank you Stefan.
On Sun, Mar 4, 2012 at 11:59 AM, Stefan Tauner stefan.tauner@student.tuwien.ac.at wrote:
Hi,
i have setup a flashrom poject at http://launchpad.net/flashrom which auto-imports the svn every 6 hours and a package archive at http://launchpad.net/~flashrom-developers/+archive/flashrom-daily where new binaries are generated once a day whenever the svn has changed.
I found about daily PPA about couple days ago here: http://flashrom.org/Downloads. And used it to collect data from several boards. Is there plan to update the wiki page with info about the new PPA?
currently there is a bug in launchpad itself that makes it impossible to use version 0.4 recipes (recipes are used to configure the autobuilders). this is the reason the package names are a bit awkward (e.g. 0.9.5.1+r1508-1-20120303 for svn r1512). it is basically named by {debversion}-{date}. it is the best i could come up with, that indicates the included source in at least some way (date), will upgrade to newer ubuntu versions when they become available and actually build in current launchpad.
another problem is that the autobuilt binaries will output this: flashrom v0.9.5.1-runknown on Linux 2.6.35-32-generic (x86_64), built with libpci 3.1.7, GCC 4.4.5, little endian i.e. no svn revision. the only way to work around this would be a second svn tree with an already (auto-)exported version of flashrom... if we could manage to set that up, we could probably build our own package too without launchpad :)
maybe it is useful anyway for someone...
-- Kind regards/Mit freundlichen Grüßen, Stefan Tauner
flashrom mailing list flashrom@flashrom.org http://www.flashrom.org/mailman/listinfo/flashrom