Bug#670679: python-debian: deb822 can't parse foreign architecture (package:any) relationships

2014-08-04 Thread Stuart Prescott
Hi John, thanks for your feedback -- I've updated the git repo accordingly in case there are further comments from anyone. cheers Stuart -- Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG

Bug#670679: python-debian: deb822 can't parse foreign architecture (package:any) relationships

2014-08-02 Thread Stuart Prescott
Hi again I've had a go at reworking the handling of multiarch qualifiers for Build- Depends. My objectives here were: * to support all the different qualifiers that are on the horizon (so :native, :i386 etc as well as :any) * to expose an API similar to dpkg's Deps.pm (or at least using the

Bug#670679: python-debian: deb822 can't parse foreign architecture (package:any) relationships

2014-08-02 Thread John Wright
Hi Stuart, On Sat, Aug 02, 2014 at 07:02:02PM +1000, Stuart Prescott wrote: Hi again I've had a go at reworking the handling of multiarch qualifiers for Build- Depends. My objectives here were: * to support all the different qualifiers that are on the horizon (so :native, :i386 etc

Bug#670679: python-debian: deb822 can't parse foreign architecture (package:any) relationships

2014-07-02 Thread Raphael Hertzog
On Mon, 08 Oct 2012, John Wright wrote: Thanks for the patchset. I've rebased it against our tip, and combined patches 2 and 3 so that tests pass at each commit. Can you take a look at the branch here:

Bug#670679: python-debian: deb822 can't parse foreign architecture (package:any) relationships

2014-06-01 Thread Stuart Prescott
Hi Stefano python-debian maintainers, Looking at the patches to support :any relationships in python-debian, I think I have to agree that adding :any and :native at the same time makes sense. https://wiki.ubuntu.com/MultiarchCross The present set of patches for :any adds a key

Bug#670679: python-debian: deb822 can't parse foreign architecture (package:any) relationships

2013-03-19 Thread paul cannon
For what it's worth, I looked over these changes, and they look good to me as far as fixing the foo:any type of arch-qualified Build-Depends. However, since dpkg and 'apt-get build-dep' already also support the foo:native syntax of arch-qualified Build-Depends, and it comes in super handy for

Bug#670679: python-debian: deb822 can't parse foreign architecture (package:any) relationships

2012-10-08 Thread John Wright
Hi Stefano, On Sat, Apr 28, 2012 at 12:40:45AM +0200, Stefano Rivera wrote: Hi submit (2012.04.28_00:33:40_+0200) This syntax isn't documented in Debian Policy, that I can see. The only mention of it I can find is in https://wiki.ubuntu.com/MultiarchHowto Err,

Bug#670679: python-debian: deb822 can't parse foreign architecture (package:any) relationships

2012-04-27 Thread Stefano Rivera
Package: python-debian Version: 0.1.21 Severity: normal Tags: patch The Ubuntu archive now has some packages with Build-Depends on gettext:any. deb822's PkgRelation parser can't handle this. This syntax isn't documented in Debian Policy, that I can see. The only mention of it I can find is in

Bug#670679: python-debian: deb822 can't parse foreign architecture (package:any) relationships

2012-04-27 Thread Stefano Rivera
Hi submit (2012.04.28_00:33:40_+0200) This syntax isn't documented in Debian Policy, that I can see. The only mention of it I can find is in https://wiki.ubuntu.com/MultiarchHowto Err, https://wiki.ubuntu.com/MultiarchSpec#Extended_semantics_of_per-architecture_package_relationships SR --