Bug#656187: reprepro: Permit to use wildcards for build-needing

2012-01-21 Thread Bernhard R. Link
package reprepro
tags 656187 + pending
thanks

* Bernhard R. Link brl...@debian.org [120119 14:13]:
 * 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).

Looks like dpkg-source was changed since I last looked, so it is
possible from the Architecture: line to see if a all package can be
built.

This this is now also implemented (available for test in git, will
be in the next version), though it will only work for source packages
createdwith a new enough dpkg-source (from at least dpkg-dev 1.16.1)
or source package building only 'all' and no 'any' packages.

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



Bug#656187: reprepro: Permit to use wildcards for build-needing

2012-01-19 Thread Bernhard R. Link
* 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



Bug#656187: reprepro: Permit to use wildcards for build-needing

2012-01-19 Thread Daniel Dehennin
Bernhard R. Link brl...@debian.org writes:

 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...

It may permit to setup a some poor man wanna-build with the rebuildd
package.

Thanks.
-- 
Daniel Dehennin
Récupérer ma clef GPG:
gpg --keyserver pgp.mit.edu --recv-keys 0x6A2540D1


pgpLptBHU4IKH.pgp
Description: PGP signature


Bug#656187: reprepro: Permit to use wildcards for build-needing

2012-01-18 Thread Daniel Dehennin
Bernhard R. Link brl...@debian.org writes:

 If I upload sources of an all package, it's not listed for the
 different architectures reprepro manages.

 Could you be a bit more specific?

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

Uploading to my repository:

#+begin_src sh
buildd@build:~$ ssh ftp@repository 'reprepro -v -b ${HOME}/reprepro 
processincoming unstable'
[...]
Exporting indices...
#+end_src

Now, my packages sources are installed in the repository, the command
apt-cache showsrc my-package shows my source package.

Then, I try:

#+begin_src sh
buildd@build:~$ ssh ftp@repository 'reprepro -v -b ${HOME}/reprepro 
build-needing unstable any'
Error: Architecture 'any' is not known!
There have been errors!

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!

buildd@build:~$ ssh ftp@repository 'reprepro -v -b ${HOME}/reprepro 
build-needing unstable amd64'
buildd@build:~$
#+end_src

If I put Architecture: any in my debian/control for the binary
package, it is listed when doing build-needing unstable amd64.

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

Regards.

-- 
Daniel Dehennin
Récupérer ma clef GPG:
gpg --keyserver pgp.mit.edu --recv-keys 0x6A2540D1


pgpHf67G7wk46.pgp
Description: PGP signature


Bug#656187: reprepro: Permit to use wildcards for build-needing

2012-01-17 Thread Daniel Dehennin
Package: reprepro
Version: 4.8.2-1
Severity: wishlist

Dear Maintainer,

Is there a way to make reprepro build-needing using wildcards and/or any
and/or all?

If I upload sources of an all package, it's not listed for the
different architectures reprepro manages.

Regards.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (90, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0+hati.1+ (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages reprepro depends on:
ii  libarchive12.8.5-5
ii  libbz2-1.0 1.0.6-1
ii  libc6  2.13-24
ii  libdb5.1   5.1.29-1
ii  libgpg-error0  1.10-2
ii  libgpgme11 1.2.0-1.4
ii  zlib1g 1:1.2.3.4.dfsg-3

Versions of packages reprepro recommends:
ii  apt  0.8.15.9

Versions of packages reprepro suggests:
ii  gnupg-agent 2.0.18-2
ii  inoticoming none
ii  lzipnone
ii  xz-lzma [lzma]  5.1.1alpha+20110809-3
ii  xz-utils5.1.1alpha+20110809-3

-- no debconf information

-- 
Daniel Dehennin
Récupérer ma clef GPG:
gpg --keyserver pgp.mit.edu --recv-keys 0x6A2540D1


pgp9JnsoEnOzr.pgp
Description: PGP signature


Bug#656187: reprepro: Permit to use wildcards for build-needing

2012-01-17 Thread Bernhard R. Link
* Daniel Dehennin daniel.dehen...@baby-gnu.org [120117 10:42]:
 Is there a way to make reprepro build-needing using wildcards and/or any
 and/or all?

The new-style wildcards might still be missing. All and any should be
hopefully working...

 If I upload sources of an all package, it's not listed for the
 different architectures reprepro manages.

Could you be a bit more specific?

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