Bug#696631: libconfig-model-dpkg-perl: '+' is allowed in package names

2012-12-28 Thread Stephen Kitt
Hi Salvatore,

On Wed, 26 Dec 2012 23:45:24 +0100, Salvatore Bonaccorso car...@debian.org
wrote:
 On Mon, Dec 24, 2012 at 02:30:23PM +0100, Stephen Kitt wrote:
  When running cme check dpkg in the gcc-mingw-w64 source, I get
  failures related to the use of '+' in a package name:
  
  Warning in 'control binary:gcc-mingw-w64 Recommends:0' value
  'g++-mingw-w64': package g is unknown. Check for typos if not a virtual
  package. Configuration item 'control binary:gcc-mingw-w64 Recommends:0'
  has a wrong value: dependency 'g++-mingw-w64' does not match grammar
  
  As far as I'm aware this package name is perfectly legal.
  Unfortunately my perl-fu doesn't extend far enough to fix this...
 
 This is correct[1]. According to Debian policy 5.6.1 Source, package
 names must consist only of lower case letters (a-z), digits (0-9),
 plus (+) and minus (-) signs, and periods (.). They must be at least
 two characters long and must start with an alphanumeric character.
 
[...]
 
 I have commited a tentative fix for this to our git repo, but would be
 good if Dominique Dumont can have a look at it before releasing.
 
 p.s.: During playing around with gcc-mingw-w64 noticed there is also
 missing support for Built-Using field. Reported this as #696768[2].
 
  [2]: http://bugs.debian.org/696768

Thanks! I had noticed the Built-Using error as well, but hadn't got round to
filing a bug for it.

Regards,

Stephen


signature.asc
Description: PGP signature


Bug#696631: libconfig-model-dpkg-perl: '+' is allowed in package names

2012-12-27 Thread Dominique Dumont
Le Wednesday 26 December 2012 23:45:24, Salvatore Bonaccorso a écrit :
 I have commited a tentative fix for this to our git repo, but would be
 good if Dominique Dumont can have a look at it before releasing.

The patch is fine with me.

Thanks for the help

Dominique


signature.asc
Description: This is a digitally signed message part.


Bug#696631: libconfig-model-dpkg-perl: '+' is allowed in package names

2012-12-26 Thread Salvatore Bonaccorso
Control: tags -1 + confirmed

Hi Stephen

On Mon, Dec 24, 2012 at 02:30:23PM +0100, Stephen Kitt wrote:
 Dear Maintainer,
 
 When running cme check dpkg in the gcc-mingw-w64 source, I get
 failures related to the use of '+' in a package name:
 
 Warning in 'control binary:gcc-mingw-w64 Recommends:0' value 
 'g++-mingw-w64': package g is unknown. Check for typos if not a virtual 
 package.
 Configuration item 'control binary:gcc-mingw-w64 Recommends:0' has a wrong 
 value:
   dependency 'g++-mingw-w64' does not match grammar
 
 As far as I'm aware this package name is perfectly legal.
 Unfortunately my perl-fu doesn't extend far enough to fix this...

This is correct[1]. According to Debian policy 5.6.1 Source, package
names must consist only of lower case letters (a-z), digits (0-9),
plus (+) and minus (-) signs, and periods (.). They must be at least
two characters long and must start with an alphanumeric character.

 [1]: http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Source

I have commited a tentative fix for this to our git repo, but would be
good if Dominique Dumont can have a look at it before releasing.

p.s.: During playing around with gcc-mingw-w64 noticed there is also
missing support for Built-Using field. Reported this as #696768[2].

 [2]: http://bugs.debian.org/696768

Regards,
Salvatore


signature.asc
Description: Digital signature


Bug#696631: libconfig-model-dpkg-perl: '+' is allowed in package names

2012-12-24 Thread Stephen Kitt
Package: libconfig-model-dpkg-perl
Version: 2.031
Severity: normal

Dear Maintainer,

When running cme check dpkg in the gcc-mingw-w64 source, I get
failures related to the use of '+' in a package name:

Warning in 'control binary:gcc-mingw-w64 Recommends:0' value 'g++-mingw-w64': 
package g is unknown. Check for typos if not a virtual package.
Configuration item 'control binary:gcc-mingw-w64 Recommends:0' has a wrong 
value:
dependency 'g++-mingw-w64' does not match grammar

As far as I'm aware this package name is perfectly legal.
Unfortunately my perl-fu doesn't extend far enough to fix this...

Regards,

Stephen


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libconfig-model-dpkg-perl depends on:
ii  libany-moose-perl 0.17-1
ii  libanyevent-http-perl 2.14-1
ii  libanyevent-perl  7.010-1
ii  libapt-pkg-perl   0.1.26+b1
ii  libconfig-model-perl  2.029-1
ii  libfile-homedir-perl  0.99-1
ii  liblog-log4perl-perl  1.29-1
ii  libmouse-perl 0.99-1
ii  libparse-recdescent-perl  1.967009+dfsg-1
ii  libsoftware-license-perl  0.103005-1
ii  libtext-autoformat-perl   1.669002-1
ii  libtext-diff-perl 1.41-1
ii  libyaml-perl  0.81-1
ii  lintian   2.5.10.3
ii  perl  5.14.2-16

Versions of packages libconfig-model-dpkg-perl recommends:
ii  libconfig-model-tkui-perl   1.337-2
ii  libmodule-corelist-perl 2.68-1
ii  perl5.14.2-16
ii  perl-modules [libmodule-corelist-perl]  5.14.2-16

libconfig-model-dpkg-perl suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org