On 2014-11-18 01:13, Thomas Goirand wrote: > Therefore, I'm sorry, but I will not work on fixing this bug (largely, > because I don't think it will help any users, because there is no user > for Ironic 2014.1.x). For me, the only time when Ironic starts to be > useful is with the Juno release (ie: 2014.2.x), so I will only put some > upgrades efforts starting on this release.
I have no clue what these packages do (besides failing in piuparts) ;-) > More over, this issue is, I believe, only happening when using SQLite, > which anyway, nobody uses (I maintain it only so that piuparts of this > kind can succeed...). piuparts could enable other databases as well to test your packages, I just enabled the "default one" i.e. that one that shows an error in the log (like sqlite3 command not found). If you prefer to test against a "real" database, give me some hints which one and how to enable it (preseeding would work for instance). > Therefore, closing this bug, without attempting to solve it. No problem. I may add Found: in future versions that show the same error, that may reopen this bug - feel free to close again if I miss this. (the piuparts-analyze script need exact version matches in the bts to mark a log as "known and bugged") Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
