On Thu, May 30, 2013 at 3:50 AM, Andreas Beckmann <[email protected]> wrote: > On 2013-05-30 05:40, Andrew Starr-Bochicchio wrote: >> Package: piuparts >> Version: 0.48ubuntu1 > > That's so outdated ... compared to 0.52 being released a few days ago.
That's just the installed version. I shouldn't have let reportbug set that. I was actually working on 0.52's unpacked source. There's an updated patch attached based on the develop branch in git. > We'd appreciate if you could test the git version on ubuntu (especially > getting a master-slave setup running). I'll try to do some testing with that sometime soon. >> Currently, if you run 'piuparts -D $distro -a $package' on a distro different >> than the host distro, you don't get the correct mirrors added to your >> sources. >> If a distro default is explicitly added using '-D', you should get that >> distro's default mirrors. This would make it easier to run piuparts against >> Debain on an Ubuntu host and vise versa. > > I need to think more about this. Especially with having > get_default_mirror() related TODO entries ... > > Do we need to add anything to distros.conf for supporting Ubuntu? > I'm primarily thinking about "partial" distros like security updates > (the equivalent to wheezy/updates) and volatile updates (aka > wheezy-updates). Ubuntu has $release-updates, $release-security, and $release-proposed. updates and security aren't interesting when testing against the development release, and proposed is never enabled by default. Though, updates and security should be used if you are testing say raring -> saucy upgrades. I wonder if some of what's in distros.conf could be generated programmatically with the help of python-distro-info? Thanks, -- Andrew Starr-Bochicchio Ubuntu Developer <https://launchpad.net/~andrewsomething> Debian Developer <http://qa.debian.org/developer.php?login=asb> PGP/GPG Key ID: D53FDCB1
0001-When-distro-defaults-are-explicitly-specified-use-th.patch
Description: Binary data
