Philipp Kern schrieb: > [Sorry about the terse reply.] > Not at all. Thanks for responding!
> On 2009-05-14, Malte Forkel <malte.for...@berlin.de> wrote: >> Well, just judging from a limited sample, all source.changes and >> i386.changes files I checked contain both Source and Binary fields. > > He spoke about the Files part. > Right, I checked that. i386.changes files contain references to .deb files, while source.changes files do not. >> There is some correlation to the Architecture field, though. All >> source.changes files have an Architecture value of "source". >> i386.changes files have Architecture values of "source i386", "source >> all", or "source i386 all". From the policy manual: >> >> In a .changes file, the Architecture field lists the architecture(s) >> of the package(s) currently being uploaded. This will be a list; >> if the source for the package is also being uploaded, the special >> entry source is also present. >> >> But uploading those packages with source.changes files produces i386.deb >> in the repository, too. >> BTW, does the combination of "all" (an architecture-independent package) > > No, unless it's autobuilt. > >> and "i386" imply, that this is a multiple binary package - some "all", >> some "i386"? > > No, that would be any. > Doesn't "any" indicate that the package could by build for any architecture, including i386? My assumption was that multiple values in the Architecture field of a i386.changes file indicate that it references .deb files for different architectures, i.e. for i386 and all. As for the architecture part of the name of a .changes file, I guess that if it references packages with different architectures, the most specific architecture is used, e.g. i386 is preferred to all whitch is preferred to source. > _source.changes is generated by passing -S to dpkg-buildpackage. It contains > only the source in the upload, no debs. _i386.changes usually contains the > i386 debs, but can also contain all debs if specified in the Architecture > field of the changes. > > NB: The changes file name does not need to match the content. But your > data gathering looks like they do. > After some more checking and thinking, I guess I know what's causing my problems: Its me, probably! I assume the source.changes files are created while I setup everything for building a package, e.g. by dh_make calling dpkg-buildpackage -S or whatever. I then use either debuild and pdebuild to build the binary packages. But while debuild replaces the source.changes file by an i386.changes file, pdebuild places the i386.changes file in /var/cache/pbuilder/result and does not replace the source.changes file. > Kind regards, > Philipp Kern > Thanks, Malte -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
