Menu

Main Menu
Talk Get Daily Search

Member's Online

    User Name
    Password

    PR1.2 & the Autobuilder

    Reply
    Page 1 of 4 | 1   2     3   | Next | Last
    StewartHolmes | # 1 | 2010-04-06, 12:36 | Report

    Hi all,

    Okay so the autobuilder has been updated to the 1.2 SDK... therefore if I upload a package in there, it'll be compiled with Qt 4.6... but my device doesn't have the dependencies for the version of Qt 4.6 the package is built with, and I can't seem to get them via apt.

    Is it really the case that new packages uploaded to the autobuilder are uninstallable until PR1.2 comes out?

    Stewart

    Edit | Forward | Quote | Quick Reply | Thanks

     
    krk969 | # 2 | 2010-04-06, 21:30 | Report

    answer is Yes, many threads discuss this.

    this might just work for some apps.(its only a hack, and a bad one )
    http://talk.maemo.org/showthread.php...495#post588495

    Edit | Forward | Quote | Quick Reply | Thanks

     
    Jaffa | # 3 | 2010-04-07, 14:02 | Report

    The community is trying to discuss possible solutions here:

    http://lists.maemo.org/pipermail/mae...il/025765.html

    Originally Posted by Jaffa
    We need to do something, both to improve the situation in -devel and -testing today, and test an approach for the next upgrade.

    The main requirements here are, I think:
    • It's not an excessive amount of work
    • It's a viable long term strategy
    • The QA process doesn't get broken

    Thoughts and comments from developers, or anyone else with a idea, will be much appreciated.
    The options outlined are:

    Originally Posted by Jaffa
    1. Deploy SDKs as they are released; treat -devel and -testing as trunk. [...]
    2. Revert the builder. [...]
    3. Hack the SDK, create some kind of hybrid. [...]
    4. Create separate repos, build queues for pre- and post-1.2. [...]
    5. Try building in each SDK in turn. [...]
    6. Case-by-case basis. [...]
    Many more details are in the mailing list post.

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following 5 Users Say Thank You to Jaffa For This Useful Post:
    danielwilms, dragly, frals, OVK, Rob1n

     
    anidel | # 4 | 2010-04-09, 03:42 | Report

    I might be dumb asking this, but now that PR1.2 will be released, how can I update my program to those who choose NOT to upgrade their tablet?

    Aniello

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following 2 Users Say Thank You to anidel For This Useful Post:
    ioan, YoDude

     
    krk969 | # 5 | 2010-04-09, 06:45 | Report

    Originally Posted by anidel View Post
    I might be dumb asking this, but now that PR1.2 will be released, how can I update my program to those who choose NOT to upgrade their tablet?

    Aniello
    I think there is already another repo created for PR1.2 knowm as fremantle-1.2, so I suppose we can add this as a repository on our devices if we continue to make branches like these . ( i honestly hope not ! )

    But then I dont think at the moment the autobuilder builds on both PR1.1 and PR1.2 and send them to each of these repos, that will also need to be done I guess.

    so in short, I dont think it can be done as it is now , or can it , debmasters ?

    Edit | Forward | Quote | Quick Reply | Thanks

     
    anidel | # 6 | 2010-04-09, 06:49 | Report

    Well today I've uploaded Xournal to Extras-devel and the only choice was "fremantle". I was actually expecting to find "fremantle 1.1" and "fremantle 1.2" or something similar to let me address a specific set of users.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    krk969 | # 7 | 2010-04-09, 06:54 | Report

    Originally Posted by anidel View Post
    Well today I've uploaded Xournal to Extras-devel and the only choice was "fremantle". I was actually expecting to find "fremantle 1.1" and "fremantle 1.2" or something similar to let me address a specific set of users.
    I think the redirection choice isnt there 'coz its been handled internally to redirect to fremanlte-1.2.
    For -devel and -test the autobuilder builds against PR1.2 and uploads the existing repos, which is why the problem of broken packages.
    Only extras , AFAIK, has this fremantle1.2 repo, where the packages being promoted from -test gets routed auto.

    so we wont get those updates from extras until PR1.2 is released.

    This is what I think is the status.

    *EDIT*
    Btw, just to let you know, that was exactly my suggestion in the mailing list to let the user decide which SDK and repo he wishes to target, and choice be given as a debain package control field .

    Edit | Forward | Quote | Quick Reply | Thanks

    Last edited by krk969; 2010-04-09 at 07:03.
    The Following 2 Users Say Thank You to krk969 For This Useful Post:
    anidel, Jaffa

     
    anidel | # 8 | 2010-04-09, 07:04 | Report

    That would help I think.. need to think more on the issue.

    As you put it, it looks like (and reality confirms) that users can't have -devel and -testing for PR1.1 while they can (of course) choose to remain on PR1.1 but only get updated from Extras.

    From this POV it seems the best solution would be to have PR1.1 -devel and -testing along with PR1.2 -devel and -testing as well.

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to anidel For This Useful Post:
    krk969

     
    krk969 | # 9 | 2010-04-09, 07:08 | Report

    just noticed a wiki page on this issue discussed in the mailing lists.

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to krk969 For This Useful Post:
    anidel

     
    Bundyo | # 10 | 2010-04-12, 21:49 | Report

    A partial solution enforcing older versions to dpkg-shlibdeps can be found here:
    http://talk.maemo.org/showpost.php?p...7&postcount=15

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following 2 Users Say Thank You to Bundyo For This Useful Post:
    attila77, krk969

     
    Page 1 of 4 | 1   2     3   | Next | Last
vBulletin® Version 3.8.8
Normal Logout