* Daniel Dehennin <daniel.dehen...@baby-gnu.org> [120118 10:54]:
> Making a source package, some python code with "Archictecture: all":
>
> #+begin_src sh
> buildd@build:~$ dpkg-source -b .
> buildd@build:~$ debsign ../*.dsc
> buildd@build:~$ dpkg-genchanges -S > ../my-pkg-sources.changes
> buildd@build:~$ debsign ../*.changes
> buildd@build:~$ dput myrepo ../my-pkg-sources.changes
> #+end_src
>
> buildd@build:~$ ssh ftp@repository 'reprepro -v -b ${HOME}/reprepro
> build-needing unstable all'
> Error: Architecture 'all' makes no sense for build-needing!
> There have been errors!
In architecture all I'd need to have a deeper look first. I'm not
sure there is a way to properly identify if an architecture 'all'
package is missing. (especially if one might have builds that build
with -B and one with -b).
> I think that architecture should be reported in the output of
> "build-needing" if wildcards are added, or if any/all are going to work.
>
> One per line, like:
>
> #+begin_src
> <PACKAGE> <VERSION> <DSC FILE> <ARCH>
> #+end_src
I'm not sure that 'any' and printing the architecture is that usefull,
but it is easy to implement, so available in git and will be in the next
version...
Bernhard R. Link
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
