Bug#872652: Problems building package

[Andreas Tille]

Hi Ghislain,

On Sun, Sep 24, 2017 at 06:54:34PM +0100, Ghislain Vaillant wrote:
> 
> On 24/09/17 11:19, Andreas Tille wrote:
> > 
> > BTW, the issue happens inside the clean target which is run *before*
> > chrooting into cowbuilder chroot.
> 
> I have pushed a new version which gets rid of this side effect. Could you
> try again with the latest tip of the master branch?

Done.

BTW, you might have noticed that I became less responsive to your
packages on SoB.  I realised now that others have uploaded which is
pretty much in line with my intention of SoB to strengthen the team.

I just wanted to let you know anyway that I "forced" myself to this
delay since I want to give you some time to push your DM application.  I
considered the time you wait for uploads pretty well spent to do this.
Otherwise I'm beaten by my own success to support sponsees to much and
spent my own time on things they could do perfectly on their own.

So hereby I'm nagging again:  Please push your DM application right now.
Its more than rectified considering your skills and I would love to stop
my sponsoring of your packages.

Thanks for considering and thanks for all your work

  Andreas.

-- 
http://fam-tille.de

Bug#872652: Problems building package

[Ghislain Vaillant]

On 24/09/17 11:19, Andreas Tille wrote:

On Sun, Sep 24, 2017 at 08:39:02AM +0100, Ghislain Vaillant wrote:


Are you sure your cowbuilder setup is ok? This is usually not a good sign:


BTW, the issue happens inside the clean target which is run *before*
chrooting into cowbuilder chroot.


I have pushed a new version which gets rid of this side effect. Could 
you try again with the latest tip of the master branch?


Ghis

Bug#872652: Problems building package

[Andreas Tille]

On Sun, Sep 24, 2017 at 08:39:02AM +0100, Ghislain Vaillant wrote:
> 
> Are you sure your cowbuilder setup is ok? This is usually not a good sign:

BTW, the issue happens inside the clean target which is run *before*
chrooting into cowbuilder chroot.

Kind regards

 Andreas. 

-- 
http://fam-tille.de

Bug#872652: Problems building package

[Andreas Tille]

On Sun, Sep 24, 2017 at 08:39:02AM +0100, Ghislain Vaillant wrote:
> 
> > $ gbp-build
> > gbp:info: Tarballs 'python-pymeasure_0.4.6.orig.tar.gz' not found at 
> > '../tarballs/'
> > gbp:info: Exporting 'WC' to 
> > '/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-tmp'
> > gbp:info: Moving 
> > '/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-tmp'
> >  to 
> > '/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-0.4.6'
> > I: using cowbuilder as pbuilder
> > dpkg-checkbuilddeps: error: Unmet build dependencies: python3-all 
> > python3-pandas python3-pyqtgraph (>= 0.9.10) python3-pytest-runner 
> > python3-pyvisa python3-serial (>= 2.7) python3-sphinx 
> > python3-sphinx-rtd-theme
> > W: Unmet build-dependency in source
> > dpkg-source: info: using options from 
> > python-pymeasure-0.4.6/debian/source/options: 
> > --extend-diff-ignore=^[^/]+\.egg-info/
> > dpkg-source: info: applying No-privacy-breach.patch
> > dh clean --with python3,sphinxdoc --buildsystem=pybuild
> > debian/rules override_dh_auto_clean
> > make[1]: Entering directory 
> > '/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-0.4.6'
> > dh_auto_clean
> > I: pybuild base:184: python3.6 setup.py clean
> > 
> > Note: Bypassing https://pypi.python.org/simple/pytest-runner/ (disallowed 
> > host; see http://bit.ly/1dg9ijs for details).
> > 
> > Couldn't find index page for 'pytest-runner' (maybe misspelled?)
> > 
> > Note: Bypassing https://pypi.python.org/simple/ (disallowed host; see 
> > http://bit.ly/1dg9ijs for details).
> > 
> > No local packages or working download links found for pytest-runner
> > Traceback (most recent call last):
> >File "setup.py", line 70, in 
> >  keywords="measure instrument experiment control automate graph plot"
> >File "/usr/lib/python3.6/distutils/core.py", line 108, in setup
> >  _setup_distribution = dist = klass(attrs)
> >File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 325, in 
> > __init__
> >  self.fetch_build_eggs(attrs['setup_requires'])
> >File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 446, in 
> > fetch_build_eggs
> >  replace_conflicting=True,
> >File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 
> > 855, in resolve
> >  dist = best[req.key] = env.best_match(req, ws, installer)
> >File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 
> > 1127, in best_match
> >  return self.obtain(req, installer)
> >File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 
> > 1139, in obtain
> >  return installer(requirement)
> >File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 518, in 
> > fetch_build_egg
> >  return cmd.easy_install(req)
> >File 
> > "/usr/lib/python3/dist-packages/setuptools/command/easy_install.py", line 
> > 691, in easy_install
> >  raise DistutilsError(msg)
> > distutils.errors.DistutilsError: Could not find suitable distribution for 
> > Requirement.parse('pytest-runner')
> > E: pybuild pybuild:283: clean: plugin distutils failed with: exit code=1: 
> > python3.6 setup.py clean
> > dh_auto_clean: pybuild --clean --test-pytest -i python{version} -p "3.6 
> > 3.5" returned exit code 13
> > debian/rules:12: recipe for target 'override_dh_auto_clean' failed
> > make[1]: *** [override_dh_auto_clean] Error 25
> > make[1]: Leaving directory 
> > '/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-0.4.6'
> > debian/rules:9: recipe for target 'clean' failed
> > make: *** [clean] Error 2
> > gbp:error: '~/bin/git-pbuilder ''' failed: it exited with 2
> > 
> > 
> > :-(
> 
> Not sure what to tell you. Both debomatic and my local sbuild do not report
> such issues.
> 
> Are you sure your cowbuilder setup is ok? This is usually not a good sign:
> 
> dpkg-checkbuilddeps: error: Unmet build dependencies [...]
> 
> And would explain why you are getting:
> 
> Could not find suitable distribution for Requirement.parse('pytest-runner')

I just did a fresh

  sudo cowbuilder --create

before - no change. :-(

Kind regards

  Andreas. 

-- 
http://fam-tille.de

Bug#872652: Problems building package

[Ghislain Vaillant]

On 23/09/17 18:15, Andreas Tille wrote:

On Sat, Sep 23, 2017 at 10:39:35AM +0100, Ghislain Vaillant wrote:

Frederic gave a hint to bug #873921.


Now that the situation with pandas / statsmodels is resolved, the package
builds fine [1].

[1] 
http://debomatic-amd64.debian.net/distribution#unstable/python-pymeasure/0.4.6-1/buildlog

Could you push it to the archive please?


$ gbp-build
gbp:info: Tarballs 'python-pymeasure_0.4.6.orig.tar.gz' not found at 
'../tarballs/'
gbp:info: Exporting 'WC' to 
'/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-tmp'
gbp:info: Moving 
'/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-tmp'
 to 
'/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-0.4.6'
I: using cowbuilder as pbuilder
dpkg-checkbuilddeps: error: Unmet build dependencies: python3-all python3-pandas 
python3-pyqtgraph (>= 0.9.10) python3-pytest-runner python3-pyvisa python3-serial 
(>= 2.7) python3-sphinx python3-sphinx-rtd-theme
W: Unmet build-dependency in source
dpkg-source: info: using options from 
python-pymeasure-0.4.6/debian/source/options: 
--extend-diff-ignore=^[^/]+\.egg-info/
dpkg-source: info: applying No-privacy-breach.patch
dh clean --with python3,sphinxdoc --buildsystem=pybuild
debian/rules override_dh_auto_clean
make[1]: Entering directory 
'/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-0.4.6'
dh_auto_clean
I: pybuild base:184: python3.6 setup.py clean

Note: Bypassing https://pypi.python.org/simple/pytest-runner/ (disallowed host; 
see http://bit.ly/1dg9ijs for details).

Couldn't find index page for 'pytest-runner' (maybe misspelled?)

Note: Bypassing https://pypi.python.org/simple/ (disallowed host; see 
http://bit.ly/1dg9ijs for details).

No local packages or working download links found for pytest-runner
Traceback (most recent call last):
   File "setup.py", line 70, in 
 keywords="measure instrument experiment control automate graph plot"
   File "/usr/lib/python3.6/distutils/core.py", line 108, in setup
 _setup_distribution = dist = klass(attrs)
   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 325, in 
__init__
 self.fetch_build_eggs(attrs['setup_requires'])
   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 446, in 
fetch_build_eggs
 replace_conflicting=True,
   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 855, 
in resolve
 dist = best[req.key] = env.best_match(req, ws, installer)
   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1127, 
in best_match
 return self.obtain(req, installer)
   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1139, 
in obtain
 return installer(requirement)
   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 518, in 
fetch_build_egg
 return cmd.easy_install(req)
   File "/usr/lib/python3/dist-packages/setuptools/command/easy_install.py", 
line 691, in easy_install
 raise DistutilsError(msg)
distutils.errors.DistutilsError: Could not find suitable distribution for 
Requirement.parse('pytest-runner')
E: pybuild pybuild:283: clean: plugin distutils failed with: exit code=1: 
python3.6 setup.py clean
dh_auto_clean: pybuild --clean --test-pytest -i python{version} -p "3.6 3.5" 
returned exit code 13
debian/rules:12: recipe for target 'override_dh_auto_clean' failed
make[1]: *** [override_dh_auto_clean] Error 25
make[1]: Leaving directory 
'/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-0.4.6'
debian/rules:9: recipe for target 'clean' failed
make: *** [clean] Error 2
gbp:error: '~/bin/git-pbuilder ''' failed: it exited with 2


:-(


Not sure what to tell you. Both debomatic and my local sbuild do not 
report such issues.


Are you sure your cowbuilder setup is ok? This is usually not a good sign:

dpkg-checkbuilddeps: error: Unmet build dependencies [...]

And would explain why you are getting:

Could not find suitable distribution for Requirement.parse('pytest-runner')

Ghis

Bug#872652: Problems building package

[Andreas Tille]

On Sat, Sep 23, 2017 at 10:39:35AM +0100, Ghislain Vaillant wrote:
> > Frederic gave a hint to bug #873921.
> 
> Now that the situation with pandas / statsmodels is resolved, the package
> builds fine [1].
> 
> [1] 
> http://debomatic-amd64.debian.net/distribution#unstable/python-pymeasure/0.4.6-1/buildlog
> 
> Could you push it to the archive please?

$ gbp-build
gbp:info: Tarballs 'python-pymeasure_0.4.6.orig.tar.gz' not found at 
'../tarballs/'
gbp:info: Exporting 'WC' to 
'/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-tmp'
gbp:info: Moving 
'/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-tmp'
 to 
'/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-0.4.6'
I: using cowbuilder as pbuilder
dpkg-checkbuilddeps: error: Unmet build dependencies: python3-all 
python3-pandas python3-pyqtgraph (>= 0.9.10) python3-pytest-runner 
python3-pyvisa python3-serial (>= 2.7) python3-sphinx python3-sphinx-rtd-theme
W: Unmet build-dependency in source
dpkg-source: info: using options from 
python-pymeasure-0.4.6/debian/source/options: 
--extend-diff-ignore=^[^/]+\.egg-info/
dpkg-source: info: applying No-privacy-breach.patch
dh clean --with python3,sphinxdoc --buildsystem=pybuild
   debian/rules override_dh_auto_clean
make[1]: Entering directory 
'/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-0.4.6'
dh_auto_clean
I: pybuild base:184: python3.6 setup.py clean 

Note: Bypassing https://pypi.python.org/simple/pytest-runner/ (disallowed host; 
see http://bit.ly/1dg9ijs for details).

Couldn't find index page for 'pytest-runner' (maybe misspelled?)

Note: Bypassing https://pypi.python.org/simple/ (disallowed host; see 
http://bit.ly/1dg9ijs for details).

No local packages or working download links found for pytest-runner
Traceback (most recent call last):
  File "setup.py", line 70, in 
keywords="measure instrument experiment control automate graph plot"
  File "/usr/lib/python3.6/distutils/core.py", line 108, in setup
_setup_distribution = dist = klass(attrs)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 325, in 
__init__
self.fetch_build_eggs(attrs['setup_requires'])
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 446, in 
fetch_build_eggs
replace_conflicting=True,
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 855, in 
resolve
dist = best[req.key] = env.best_match(req, ws, installer)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1127, 
in best_match
return self.obtain(req, installer)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1139, 
in obtain
return installer(requirement)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 518, in 
fetch_build_egg
return cmd.easy_install(req)
  File "/usr/lib/python3/dist-packages/setuptools/command/easy_install.py", 
line 691, in easy_install
raise DistutilsError(msg)
distutils.errors.DistutilsError: Could not find suitable distribution for 
Requirement.parse('pytest-runner')
E: pybuild pybuild:283: clean: plugin distutils failed with: exit code=1: 
python3.6 setup.py clean 
dh_auto_clean: pybuild --clean --test-pytest -i python{version} -p "3.6 3.5" 
returned exit code 13
debian/rules:12: recipe for target 'override_dh_auto_clean' failed
make[1]: *** [override_dh_auto_clean] Error 25
make[1]: Leaving directory 
'/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-0.4.6'
debian/rules:9: recipe for target 'clean' failed
make: *** [clean] Error 2
gbp:error: '~/bin/git-pbuilder ''' failed: it exited with 2


:-(

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#872652: Problems building package

[Ghislain Vaillant]

On Mon, 4 Sep 2017 13:16:46 +0200 Andreas Tille  wrote:

Hi Ghislain,

On Mon, Sep 04, 2017 at 11:47:09AM +0200, Ghislain Vaillant wrote:
> Hi Andreas, how are you doing?

Fine thank you.
 
> On 04/09/17 11:27, Andreas Tille wrote:
> 
> I just ran a test build on debomatic, and it is now riddled with "undefined

> symbol: PyFPE_jbuf" errors which were not there before.
> 
> I believe this is symptomatic of a larger issue within the archive, since

> other Python packages I maintain have had a similar error raised by their
> respective autopkgtests recently. *sigh*

Frederic gave a hint to bug #873921.


Now that the situation with pandas / statsmodels is resolved, the 
package builds fine [1].


[1] 
http://debomatic-amd64.debian.net/distribution#unstable/python-pymeasure/0.4.6-1/buildlog


Could you push it to the archive please?

Cheers,
Ghis

Bug#872652: Problems building package

[Andreas Tille]

Hi Ghislain,

On Mon, Sep 04, 2017 at 11:47:09AM +0200, Ghislain Vaillant wrote:
> Hi Andreas, how are you doing?

Fine thank you.
 
> On 04/09/17 11:27, Andreas Tille wrote:
> 
> I just ran a test build on debomatic, and it is now riddled with "undefined
> symbol: PyFPE_jbuf" errors which were not there before.
> 
> I believe this is symptomatic of a larger issue within the archive, since
> other Python packages I maintain have had a similar error raised by their
> respective autopkgtests recently. *sigh*

Frederic gave a hint to bug #873921.
 
> > PS: What about your DM application?
> Still pending. Priority is low at the moment due to work.

I honestly think that you should shift the priority of your application
higher than any packaging.  I might lower my priority on sponsoring your
packages otherwise. :-P

Honestly, you should seriously apply as DM pretty soon.  It makes no
sense to put the sponsoring work on other DDs all the time.

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#872652: Problems building package

[PICCA Frederic-Emmanuel]

Hello guyes,

look at here


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873921

:((

Bug#872652: Problems building package

[Ghislain Vaillant]

Hi Andreas, how are you doing?

On 04/09/17 11:27, Andreas Tille wrote:

gbp:info: Tarballs 'python-pymeasure_0.4.6.orig.tar.gz' not found at 
'../tarballs/'
gbp:info: Exporting 'WC' to 
'/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-tmp'
gbp:info: Moving 
'/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-tmp'
 to 
'/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-0.4.6'
I: using cowbuilder as pbuilder
dpkg-checkbuilddeps: error: Unmet build dependencies: python3-pyqtgraph (>= 
0.9.10) python3-pytest python3-pytest-runner python3-pyvisa python3-serial (>= 2.7)
W: Unmet build-dependency in source
dpkg-source: info: using options from 
python-pymeasure-0.4.6/debian/source/options: 
--extend-diff-ignore=^[^/]+\.egg-info/
dpkg-source: info: applying No-privacy-breach.patch
dh clean --with python3,sphinxdoc --buildsystem=pybuild
debian/rules override_dh_auto_clean
make[1]: Entering directory 
'/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-0.4.6'
dh_auto_clean
I: pybuild base:184: python3.6 setup.py clean

Note: Bypassing https://pypi.python.org/simple/pytest-runner/ (disallowed host; 
see http://bit.ly/1dg9ijs for details).

Couldn't find index page for 'pytest-runner' (maybe misspelled?)

Note: Bypassing https://pypi.python.org/simple/ (disallowed host; see 
http://bit.ly/1dg9ijs for details).

No local packages or working download links found for pytest-runner
Traceback (most recent call last):
   File "setup.py", line 70, in 
 keywords="measure instrument experiment control automate graph plot"
   File "/usr/lib/python3.6/distutils/core.py", line 108, in setup
 _setup_distribution = dist = klass(attrs)
   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 325, in 
__init__
 self.fetch_build_eggs(attrs['setup_requires'])
   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 446, in 
fetch_build_eggs
 replace_conflicting=True,
   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 855, 
in resolve
 dist = best[req.key] = env.best_match(req, ws, installer)
   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1127, 
in best_match
 return self.obtain(req, installer)
   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1139, 
in obtain
 return installer(requirement)
   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 518, in 
fetch_build_egg
 return cmd.easy_install(req)
   File "/usr/lib/python3/dist-packages/setuptools/command/easy_install.py", 
line 691, in easy_install
 raise DistutilsError(msg)
distutils.errors.DistutilsError: Could not find suitable distribution for 
Requirement.parse('pytest-runner')


This error is happening when running the clean command with Python 3...


E: pybuild pybuild:283: clean: plugin distutils failed with: exit code=1: 
python3.6 setup.py clean
dh_auto_clean: pybuild --clean --test-pytest -i python{version} -p "3.6 3.5" 
returned exit code 13
debian/rules:12: recipe for target 'override_dh_auto_clean' failed
make[1]: *** [override_dh_auto_clean] Error 25
make[1]: Leaving directory 
'/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-0.4.6'
debian/rules:9: recipe for target 'clean' failed
make: *** [clean] Error 2
gbp:error: '~/bin/git-pbuilder ''' failed: it exited with 2


The package python-pytest-runner is installed on my local maching.


...so you need python3-pytest-runner.

I just ran a test build on debomatic, and it is now riddled with 
"undefined symbol: PyFPE_jbuf" errors which were not there before.


I believe this is symptomatic of a larger issue within the archive, 
since other Python packages I maintain have had a similar error raised 
by their respective autopkgtests recently. *sigh*



Kind regards

Andreas.

PS: What about your DM application?

Still pending. Priority is low at the moment due to work.

Cheers,
Ghis

Bug#872652: Problems building package

[Andreas Tille]

Hi Ghislain,

when using gbp buildpackage I get


gbp:info: Tarballs 'python-pymeasure_0.4.6.orig.tar.gz' not found at 
'../tarballs/'
gbp:info: Exporting 'WC' to 
'/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-tmp'
gbp:info: Moving 
'/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-tmp'
 to 
'/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-0.4.6'
I: using cowbuilder as pbuilder
dpkg-checkbuilddeps: error: Unmet build dependencies: python3-pyqtgraph (>= 
0.9.10) python3-pytest python3-pytest-runner python3-pyvisa python3-serial (>= 
2.7)
W: Unmet build-dependency in source
dpkg-source: info: using options from 
python-pymeasure-0.4.6/debian/source/options: 
--extend-diff-ignore=^[^/]+\.egg-info/
dpkg-source: info: applying No-privacy-breach.patch
dh clean --with python3,sphinxdoc --buildsystem=pybuild
   debian/rules override_dh_auto_clean
make[1]: Entering directory 
'/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-0.4.6'
dh_auto_clean
I: pybuild base:184: python3.6 setup.py clean 

Note: Bypassing https://pypi.python.org/simple/pytest-runner/ (disallowed host; 
see http://bit.ly/1dg9ijs for details).

Couldn't find index page for 'pytest-runner' (maybe misspelled?)

Note: Bypassing https://pypi.python.org/simple/ (disallowed host; see 
http://bit.ly/1dg9ijs for details).

No local packages or working download links found for pytest-runner
Traceback (most recent call last):
  File "setup.py", line 70, in 
keywords="measure instrument experiment control automate graph plot"
  File "/usr/lib/python3.6/distutils/core.py", line 108, in setup
_setup_distribution = dist = klass(attrs)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 325, in 
__init__
self.fetch_build_eggs(attrs['setup_requires'])
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 446, in 
fetch_build_eggs
replace_conflicting=True,
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 855, in 
resolve
dist = best[req.key] = env.best_match(req, ws, installer)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1127, 
in best_match
return self.obtain(req, installer)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1139, 
in obtain
return installer(requirement)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 518, in 
fetch_build_egg
return cmd.easy_install(req)
  File "/usr/lib/python3/dist-packages/setuptools/command/easy_install.py", 
line 691, in easy_install
raise DistutilsError(msg)
distutils.errors.DistutilsError: Could not find suitable distribution for 
Requirement.parse('pytest-runner')
E: pybuild pybuild:283: clean: plugin distutils failed with: exit code=1: 
python3.6 setup.py clean 
dh_auto_clean: pybuild --clean --test-pytest -i python{version} -p "3.6 3.5" 
returned exit code 13
debian/rules:12: recipe for target 'override_dh_auto_clean' failed
make[1]: *** [override_dh_auto_clean] Error 25
make[1]: Leaving directory 
'/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-0.4.6'
debian/rules:9: recipe for target 'clean' failed
make: *** [clean] Error 2
gbp:error: '~/bin/git-pbuilder ''' failed: it exited with 2


The package python-pytest-runner is installed on my local maching.

Kind regards

   Andreas.

PS: What about your DM application?


-- 
http://fam-tille.de

Re: Building package under kfreebsd/hurd

[Elías Alejandro]

Thanks!. I will try your suggestions.

Best regards.

Elías

On Mon, Nov 7, 2016 at 8:18 AM, Christian Seiler  wrote:
> On 11/07/2016 12:46 AM, Elías Alejandro wrote:
>> I wonder if there's a way to build packages for distinct
>> architectures, specifically for
>> Hurd or Kfreebsd. Do I have to create a new installation or use qemu?.
>
> In my experience the easiest way to do so is to use a virtual
> machine (I prefer libvirt + virt-manager with Qemu for that),
> boot the machine, install an SSH server and
>
> In the case of Hurd, you really don't want to use that on your
> bare-metal hardware, because last time I checked it didn't
> support USB yet. (If you don't need USB you can of course use
> it. ;-)) kFreeBSD is not a problem in that regard, but unless
> your system is really RAM-starved a VM is still much easier to
> handle.
>
> Note that it's not completely trivial to set up these machines.
> The problem is that most installation media you can find are
> a bit older, and if you've ever tried to install testing/sid
> with an older installer, you can see that it often doesn't
> quite work because sid will have moved on quite a bit. Plus
> a lot of the documentation you find is a bit outdated for
> both archs - there is more current documentation, but when
> searching you more often than not find the outdated docs in
> my experience, before you find the current ones.
>
> In the case of Hurd Samuel Thibault provides premade images
> you can use:
> https://people.debian.org/~sthibault/hurd-i386/README
> https://people.debian.org/~sthibault/hurd-i386/
> I suspect that's going to be the easiest way of setting up a
> VM there. (Please do a dist-upgraded before you actually use
> them to try stuff though, they are relatively up to date, but
> aren't daily images.)
>
> In the case of kFreeBSD, I'm not completely sure anymore,
> but if I remember correctly, I used the Jessie rc3 installer
> to install the VM and then dist-upgraded to sid (by changing
> the sources.list):
> http://cdimage.debian.org/mirror/cdimage/archive/jessie_di_rc3/kfreebsd-amd64/iso-cd/
> (That may or may not work, depending on whether I remember
> correctly.)
>
> In both cases (Hurd, kFreeBSD) please be aware that while a
> lot of the everyday userland is still the same as with the
> Linux ports (e.g. ls, cp, etc.), many administrative commands
> are quite different or at least have different options / a
> different output. Especially Hurd can be quite weird when you
> first come in contact with it; once you get to know some of
> the concepts and ideas behind it, it's actually really cool,
> but there's a bit of a learning curve there.
>
> Hope that helps.
>
>> [1]https://wiki.debian.org/qemubuilder
>
> I haven't tried that yet, but from reading the wiki page it
> looks to me that it's mostly a Linux thing - and while there
> is no inherent reason why fully-fledged VMs with Hurd or
> kFreeBSD wouldn't work in principle with something like that,
> I suspect that you'd need to fix a lot of things to make it
> work. (I may be wrong though.) It's probably easier to just
> use a virtual machine manually yourself.
>
> Regards,
> Christian

Re: Building package under kfreebsd/hurd

[Christian Seiler]

On 11/07/2016 12:46 AM, Elías Alejandro wrote:
> I wonder if there's a way to build packages for distinct
> architectures, specifically for
> Hurd or Kfreebsd. Do I have to create a new installation or use qemu?.

In my experience the easiest way to do so is to use a virtual
machine (I prefer libvirt + virt-manager with Qemu for that),
boot the machine, install an SSH server and 

In the case of Hurd, you really don't want to use that on your
bare-metal hardware, because last time I checked it didn't
support USB yet. (If you don't need USB you can of course use
it. ;-)) kFreeBSD is not a problem in that regard, but unless
your system is really RAM-starved a VM is still much easier to
handle.

Note that it's not completely trivial to set up these machines.
The problem is that most installation media you can find are
a bit older, and if you've ever tried to install testing/sid
with an older installer, you can see that it often doesn't
quite work because sid will have moved on quite a bit. Plus
a lot of the documentation you find is a bit outdated for
both archs - there is more current documentation, but when
searching you more often than not find the outdated docs in
my experience, before you find the current ones.

In the case of Hurd Samuel Thibault provides premade images
you can use:
https://people.debian.org/~sthibault/hurd-i386/README
https://people.debian.org/~sthibault/hurd-i386/
I suspect that's going to be the easiest way of setting up a
VM there. (Please do a dist-upgraded before you actually use
them to try stuff though, they are relatively up to date, but
aren't daily images.)

In the case of kFreeBSD, I'm not completely sure anymore,
but if I remember correctly, I used the Jessie rc3 installer
to install the VM and then dist-upgraded to sid (by changing
the sources.list):
http://cdimage.debian.org/mirror/cdimage/archive/jessie_di_rc3/kfreebsd-amd64/iso-cd/
(That may or may not work, depending on whether I remember
correctly.)

In both cases (Hurd, kFreeBSD) please be aware that while a
lot of the everyday userland is still the same as with the
Linux ports (e.g. ls, cp, etc.), many administrative commands
are quite different or at least have different options / a
different output. Especially Hurd can be quite weird when you
first come in contact with it; once you get to know some of
the concepts and ideas behind it, it's actually really cool,
but there's a bit of a learning curve there.

Hope that helps.

> [1]https://wiki.debian.org/qemubuilder

I haven't tried that yet, but from reading the wiki page it
looks to me that it's mostly a Linux thing - and while there
is no inherent reason why fully-fledged VMs with Hurd or
kFreeBSD wouldn't work in principle with something like that,
I suspect that you'd need to fix a lot of things to make it
work. (I may be wrong though.) It's probably easier to just
use a virtual machine manually yourself.

Regards,
Christian

Re: Building package under kfreebsd/hurd

[Paul Wise]

On Mon, Nov 7, 2016 at 7:46 AM, Elías Alejandro wrote:

> I wonder if there's a way to build packages for distinct
> architectures, specifically for Hurd or Kfreebsd.

The options for this include:

Cross-building
Virtual machine
Porterboxen
Your hardware

> Do I have to create a new installation or use qemu?

Those are probably the best options.

> My PC is a i386 and I want to fix a FTBFS bug for these architectures.

Thanks for taking care of the less popular ports of Debian.

> I was reading about qemubuilder[1] but I couldn't see a specific
> workaround for these architectures.

I guess you need to pass the --architecture hurd-i386 pbuilder option
to qemubuilder when creating the initial image and when building
packages.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Building package under kfreebsd/hurd

[Elías Alejandro]

Hello,
I wonder if there's a way to build packages for distinct
architectures, specifically for
Hurd or Kfreebsd. Do I have to create a new installation or use qemu?.
My PC is a i386 and I want to fix a FTBFS bug for these architectures.
I was reading about qemubuilder[1] but I couldn't see a specific
workaround for these architectures.

[1]https://wiki.debian.org/qemubuilder


Best regards,
Elías Alejandro

Re: Building package locally for different architectures

[Dmitry Bogatov]

[2016-08-30 19:20] Jakub Wilk 
>
> part   text/plain 965
> [Disclaimer: I don't know anything about reprepro.]
>
> * Dmitry Bogatov , 2016-08-30, 17:38:
> >$ dpkg-source -b . # fine
> >$ debsign -m kact...@gnu.org ../*.dsc # fine
> >$ sbuild -d pure -c jessie # fine
> >$ debsign --no-re-sign ../*.changes # fine, signed with my key
> >$ dput local ../*.changes # fine, local -> my reprepro instance
> >$ rm ../*.changes # time to prepare for i386
> >$ sbuild -d pure -c jessie --build i386 --arch i386 # fine
>
> You don't need "--build i386" here.

Nice to know.

> >$ debsign --no-re-sign ../*.changes # fine
> >$ dput local ../*.changes
> > File "pool/main/s/sudo/sudo_1.8.10p3-1+deb8u3pure1.dsc" is already 
> > registered with different checksums!
> > md5 expected: 6844ffcf32db1c64eb4106161d0d3551, got: 
> > c75e41a14c4c2d860b6d715f22aa9f58
>
> Is your sbuild configured to build source package by default
> ("$build_source = 1" in /etc/sbuild/sbuild.conf)?
> If yes, I guess you'll need to turn it off (--no-source) for the second
> build.

Thanks! It solved my problem.

-- 
Accept: text/plain, text/x-diff
Accept-Language: eo,en,ru
X-Web-Site: sinsekvu.github.io

Re: Building package locally for different architectures

[Jakub Wilk]

[Disclaimer: I don't know anything about reprepro.]

* Dmitry Bogatov , 2016-08-30, 17:38:

$ dpkg-source -b . # fine
$ debsign -m kact...@gnu.org ../*.dsc # fine
$ sbuild -d pure -c jessie # fine
$ debsign --no-re-sign ../*.changes # fine, signed with my key
$ dput local ../*.changes # fine, local -> my reprepro instance
$ rm ../*.changes # time to prepare for i386
$ sbuild -d pure -c jessie --build i386 --arch i386 # fine


You don't need "--build i386" here.


$ debsign --no-re-sign ../*.changes # fine
$ dput local ../*.changes
File "pool/main/s/sudo/sudo_1.8.10p3-1+deb8u3pure1.dsc" is already 
registered with different checksums!
md5 expected: 6844ffcf32db1c64eb4106161d0d3551, got: 
c75e41a14c4c2d860b6d715f22aa9f58


Is your sbuild configured to build source package by default 
("$build_source = 1" in /etc/sbuild/sbuild.conf)?
If yes, I guess you'll need to turn it off (--no-source) for the second 
build.


--
Jakub Wilk

Building package locally for different architectures

[Dmitry Bogatov]

Hello!

I am trying to create personal repository, that would contain
locally-rebuilt packages for i386 and amd64.

I set up reprepro, and trying to do following, where  is root of
source package directory.

$ dpkg-source -b . # fine
$ debsign -m kact...@gnu.org ../*.dsc # fine
$ sbuild -d pure -c jessie # fine
$ debsign --no-re-sign ../*.changes # fine, signed with my key
$ dput local ../*.changes # fine, local -> my reprepro instance
$ rm ../*.changes # time to prepare for i386
$ sbuild -d pure -c jessie --build i386 --arch i386 # fine
$ debsign --no-re-sign ../*.changes # fine
$ dput local ../*.changes
File "pool/main/s/sudo/sudo_1.8.10p3-1+deb8u3pure1.dsc" is already 
registered with different checksums!
md5 expected: 6844ffcf32db1c64eb4106161d0d3551, got: 
c75e41a14c4c2d860b6d715f22aa9f58
sha1 expected: 6d5dc281662c1ea580f86e9fd20e51722183fac8, got: 
c581dea8ac82520fb7e5f81ec7675000a9479639
sha256 expected: 
eb2f36012c35ddd6f84bc0ababa533639ac749c7ad8d6a3811c3e30875750876, got: 
e4a813aee4759df861a35827ad19159f
405fbcd3eccea382d7a6b16d37d7e1da

Any suggestions, please? Or, maybe more simple way to get dists/pool
repository with my packages, built for both amd64 and i386.

-- 
Accept: text/plain, text/x-diff
Accept-Language: eo,en,ru
X-Web-Site: sinsekvu.github.io


pgpYV_eW7FZbY.pgp
Description: PGP signature

Re: building package with different libs

[Peter Pentchev]

On Wed, Oct 29, 2008 at 06:00:15PM +0100, Adeodato wrote:
 * Peter Pentchev [Wed, 29 Oct 2008 18:09:07 +0200]:
 
   If the different implementations conflict among them, I don't think you
   can build all three SL{1,2,3} binary packages from the same source
   package.
 
  Well, actually, you can - just look at the various apache2 packages.
  However, the build mechanism has to be a bit complicated...
 
 Care to ellaborate? I don't think in that case the build-dependencies
 conflict, OR they are built from the same source package.

Oh, sorry, my mistake.  A momentary lapse of reason made me forget that
the discussion is about conflicting build dependencies, not just about
conflicting binary packages.  Apologies all around.

G'luck,
Peter

-- 
Peter Pentchev  [EMAIL PROTECTED][EMAIL PROTECTED][EMAIL PROTECTED]
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint FDBA FD79 C26F 3C51 C95E  DF9E ED18 B68D 1619 4553
What would this sentence be like if pi were 3?


pgpWMvVczwnIu.pgp
Description: PGP signature

Re: building package with different libs

[Adeodato Simó]

* Thorsten Alteholz [Fri, 17 Oct 2008 20:06:09 +0200]:

 Hi,

Hello,

 I need some advice on building packages with different libs.
 Assuming that I have software S which needs to be linked against library L.
 For whatever reason there are several implementations (L1, L2, L3) of 
 this library available. Each of them has its advantages and it would be 
 fine
 to build three packages SL1, SL2 and SL3.
 Unfortunately L1, L2 and L3 conflict each other. So what would be the 
 best way to build all three packages from one source package? Is this 
 possible at all?

 To make this a bit more realistic: It is about package meep-mpi.
 Currently it uses libhdf5-serial and there is a requet to build it with
 libhdf5-mpich and libhdf5-openmpi. So my Build-Depends: in the source section
 needs to contain either libhdf5-serial-dev, libhdf5-mpich-dev or
 libhdf5-openmpi-dev. Is it still possible to build package 
 meep-mpi-hdf5serial,
 meep-mpi-hdf5mpich and meep-mpi-hdf5openmpi at the same time?

If the different implementations conflict among them, I don't think you
can build all three SL{1,2,3} binary packages from the same source
package.

Cheers,

-- 
Adeodato Simó dato at net.com.org.es
Debian Developer  adeodato at debian.org
 
A hacker does for love what other would not do for money.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: building package with different libs

[Peter Pentchev]

On Wed, Oct 29, 2008 at 04:30:25PM +0100, Adeodato Sim?? wrote:
 * Thorsten Alteholz [Fri, 17 Oct 2008 20:06:09 +0200]:
 
  Hi,
 
 Hello,
 
  I need some advice on building packages with different libs.
  Assuming that I have software S which needs to be linked against library L.
  For whatever reason there are several implementations (L1, L2, L3) of 
  this library available. Each of them has its advantages and it would be 
  fine
  to build three packages SL1, SL2 and SL3.
  Unfortunately L1, L2 and L3 conflict each other. So what would be the 
  best way to build all three packages from one source package? Is this 
  possible at all?
 
  To make this a bit more realistic: It is about package meep-mpi.
  Currently it uses libhdf5-serial and there is a requet to build it with
  libhdf5-mpich and libhdf5-openmpi. So my Build-Depends: in the source 
  section
  needs to contain either libhdf5-serial-dev, libhdf5-mpich-dev or
  libhdf5-openmpi-dev. Is it still possible to build package 
  meep-mpi-hdf5serial,
  meep-mpi-hdf5mpich and meep-mpi-hdf5openmpi at the same time?
 
 If the different implementations conflict among them, I don't think you
 can build all three SL{1,2,3} binary packages from the same source
 package.

Well, actually, you can - just look at the various apache2 packages.
However, the build mechanism has to be a bit complicated...

G'luck,
Peter

-- 
Peter Pentchev  [EMAIL PROTECTED][EMAIL PROTECTED][EMAIL PROTECTED]
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint FDBA FD79 C26F 3C51 C95E  DF9E ED18 B68D 1619 4553
When you are not looking at it, this sentence is in Spanish.


pgpny0U9CIfPO.pgp
Description: PGP signature

Re: building package with different libs

[Adeodato Simó]

* Peter Pentchev [Wed, 29 Oct 2008 18:09:07 +0200]:

  If the different implementations conflict among them, I don't think you
  can build all three SL{1,2,3} binary packages from the same source
  package.

 Well, actually, you can - just look at the various apache2 packages.
 However, the build mechanism has to be a bit complicated...

Care to ellaborate? I don't think in that case the build-dependencies
conflict, OR they are built from the same source package.

-- 
Adeodato Simó dato at net.com.org.es
Debian Developer  adeodato at debian.org
 
Man is certainly stark mad; he cannot make a flea, yet he makes gods by the
dozens.
-- Michel de Montaigne


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: building package with different libs

[George Danchev]

On Wednesday 29 October 2008 18:09:07 Peter Pentchev wrote:
 On Wed, Oct 29, 2008 at 04:30:25PM +0100, Adeodato Sim?? wrote:
  * Thorsten Alteholz [Fri, 17 Oct 2008 20:06:09 +0200]:
   Hi,
 
  Hello,
 
   I need some advice on building packages with different libs.
   Assuming that I have software S which needs to be linked against
   library L. For whatever reason there are several implementations (L1,
   L2, L3) of this library available. Each of them has its advantages and
   it would be fine
   to build three packages SL1, SL2 and SL3.
   Unfortunately L1, L2 and L3 conflict each other. So what would be the
   best way to build all three packages from one source package? Is this
   possible at all?
  
   To make this a bit more realistic: It is about package meep-mpi.
   Currently it uses libhdf5-serial and there is a requet to build it with
   libhdf5-mpich and libhdf5-openmpi. So my Build-Depends: in the source
   section needs to contain either libhdf5-serial-dev, libhdf5-mpich-dev
   or libhdf5-openmpi-dev. Is it still possible to build package
   meep-mpi-hdf5serial, meep-mpi-hdf5mpich and meep-mpi-hdf5openmpi at the
   same time?
 
  If the different implementations conflict among them, I don't think you
  can build all three SL{1,2,3} binary packages from the same source
  package.

 Well, actually, you can - just look at the various apache2 packages.
 However, the build mechanism has to be a bit complicated...

Actually if you have a single source package (as mentioned by Thorsten):
* you can not: since your build-depends and build-conflicts are unsatisfiable 
and buildd's would give up in the very first stage, before even seeing any 
dark magic in debian/rules
* you must not: because of Policy #7.7

Having multiple source packages declaring satisfiable build-depends, 
build-conflict, etc. would be a course of action (although ugly because of 
dups), but I would certainly check or ask if these L1, L2, L3 libraries 
really need to conflict each other in the first place.

-- 
pub 4096R/0E4BD0AB 2003-03-18 people.fccf.net/danchev/key pgp.mit.edu


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

building package with different libs

[Thorsten Alteholz]

Hi,

I need some advice on building packages with different libs.
Assuming that I have software S which needs to be linked against library L.
For whatever reason there are several implementations (L1, L2, L3) of this 
library available. Each of them has its advantages and it would be fine

to build three packages SL1, SL2 and SL3.
Unfortunately L1, L2 and L3 conflict each other. So what would be the best 
way to build all three packages from one source package? Is this possible at 
all?


To make this a bit more realistic: It is about package meep-mpi.
Currently it uses libhdf5-serial and there is a requet to build it with
libhdf5-mpich and libhdf5-openmpi. So my Build-Depends: in the source section
needs to contain either libhdf5-serial-dev, libhdf5-mpich-dev or
libhdf5-openmpi-dev. Is it still possible to build package meep-mpi-hdf5serial,
meep-mpi-hdf5mpich and meep-mpi-hdf5openmpi at the same time?

Best regards
Thorsten

PS. I am aware that it should be better meep-mpi-hdf5mpich and
 meep-openmpi-hdf5openmpi, but this is another issue...


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Building package,

[Elías A. M.]

Hi,
Somebody  know why when I build the package, show me:
dpkg-shlibdeps: warning: debian/pack/usr/games/pack shouldn't be linked with
libpthread.so.0 (it uses none of its symbols).

and,

dpkg-gencontrol: warning: unknown substitution variable ${misc:Depends}

Those two warnings, show me. But the lintian test is ok.

Thanks for advance,

Re: Building package,

[David Paleino]

On Thu, 2 Oct 2008 15:03:40 -0500, Elías A. M. wrote:

 Hi,
 Somebody  know why when I build the package, show me:
 dpkg-shlibdeps: warning: debian/pack/usr/games/pack shouldn't be linked with
 libpthread.so.0 (it uses none of its symbols).

Try passing -Wl,--as-needed into LDFLAGS to the compiler (in debian/rules,
configure target usually). Be warned that this might break your package
unexpectedly!

 dpkg-gencontrol: warning: unknown substitution variable ${misc:Depends}

You can safely ignore this warning.

Kindly,
David

-- 
 . ''`.  Debian maintainer | http://wiki.debian.org/DavidPaleino
 : :'  : Linuxer #334216 --|-- http://www.hanskalabs.net/
 `. `'`  GPG: 1392B174 | http://snipr.com/qa_page
   `-   2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174


signature.asc
Description: PGP signature

Re: Building package,

[Luca Bruno]

On Thu, Oct 02, 2008 at 03:03:40PM -0500, =?ISO-8859-1?Q?El=EDas_A._M._ wrote:
 Hi,

Hi I'm not a developer but I try to suggest you.

 Somebody  know why when I build the package, show me:
 dpkg-shlibdeps: warning: debian/pack/usr/games/pack shouldn't be linked with
 libpthread.so.0 (it uses none of its symbols).


Your package is linking against libpthread and it might not be used. If your
program uses it, then ignore the warning. If your program doesn't really use
it, add --as-needed in the LDFLAGS in your debian/rules.
 
 and,
 
 dpkg-gencontrol: warning: unknown substitution variable ${misc:Depends}
 
 Those two warnings, show me. But the lintian test is ok.


I think you can ignore this one.
 
 Thanks for advance,

You're welcome, I'm at the beggining just like you.

-- 
http://syx.googlecode.com - Smalltalk YX
http://lethalman.blogspot.com - Thoughts about computer technologies
http://www.debian.org - The Universal Operating System


signature.asc
Description: Digital signature

Unheeded warnings from build tools (was: Building package,)

[Ben Finney]

David Paleino [EMAIL PROTECTED] writes:

 On Thu, 2 Oct 2008 15:03:40 -0500, Elías A. M. wrote:
  dpkg-gencontrol: warning: unknown substitution variable ${misc:Depends}
 
 You can safely ignore this warning.

Luca Bruno [EMAIL PROTECTED] writes:

 On Thu, Oct 02, 2008 at 03:03:40PM -0500, =?ISO-8859-1?Q?El=EDas_A._M._ wrote:
  dpkg-gencontrol: warning: unknown substitution variable ${misc:Depends}
 
 I think you can ignore this one.

I think it'sa bad situation when a build tool emits a warning that is
routinely ignored; it commonly leads to masking real problems.

The correct solution is for the warning to go away. Either this *is*
something that needs attention, or it is not. In the former case, what
is the problem and what is the solution? In the latter case, why is
the warning there at all?

-- 
 \  “Ocean, n. A body of water occupying about two-thirds of a |
  `\ world made for man — who has no gills.” —Ambrose Bierce, _The |
_o__)Devil's Dictionary_, 1906 |
Ben Finney


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Building package,

[Charles Plessy]

 On Thu, Oct 02, 2008 at 03:03:40PM -0500, =?ISO-8859-1?Q?El=EDas_A._M._ wrote:
  dpkg-shlibdeps: warning: debian/pack/usr/games/pack shouldn't be linked with
  libpthread.so.0 (it uses none of its symbols).
 
Le Thu, Oct 02, 2008 at 11:15:20PM +0200, Luca Bruno a écrit :
 Your package is linking against libpthread and it might not be used. If your
 program uses it, then ignore the warning. If your program doesn't really use
 it, add --as-needed in the LDFLAGS in your debian/rules.

Hi all,

Is it the kind of issue that is worth reporting upstream? If yes, could
somebody update http://wiki.debian.org/GettingPackaged (I do not
understand enough the issue for doing it myself). It would then be easy
to inform upstream of the unnecessary links and point at this page for
the explanations.

Have a nice day,

-- 
Charles Plessy
Debian Med packaging team,
Tsurumi, Kanagawa, Japan


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Building package,

[Felipe Sateler]

Luca Bruno wrote:

 On Thu, Oct 02, 2008 at 03:03:40PM -0500, =?ISO-8859-1?Q?El=EDas_A._M._ wrote:
 Hi,
 
 Hi I'm not a developer but I try to suggest you.
 
 Somebody  know why when I build the package, show me:
 dpkg-shlibdeps: warning: debian/pack/usr/games/pack shouldn't be linked with
 libpthread.so.0 (it uses none of its symbols).

 
 Your package is linking against libpthread and it might not be used. If your
 program uses it, then ignore the warning. If your program doesn't really use
 it, add --as-needed in the LDFLAGS in your debian/rules.

When (for some reason) -pthread is passed to gcc, the -Wl,--as-needed flag won't
unlink it (newlines added for clarity):

% gcc -o test test.c
% objdump -p test | grep NEEDED
  NEEDED  libc.so.6

% gcc -pthread -o test test.c
% objdump -p test | grep NEEDED
  NEEDED  libpthread.so.0
  NEEDED  libc.so.6

% gcc -lpthread -o test test.c
% objdump -p test | grep NEEDED
  NEEDED  libpthread.so.0
  NEEDED  libc.so.6

% gcc -Wl,--as-needed -lpthread -o test test.c
% objdump -p test | grep NEEDED
  NEEDED  libc.so.6

% gcc -Wl,--as-needed -pthread -o test test.c
% objdump -p test | grep NEEDED
  NEEDED  libpthread.so.0
  NEEDED  libc.so.6

%


-- 

  Felipe Sateler


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Building package,

[Elías A. M.]

Hi again:
I tried your suggests, but I don't have successful
I put, my debian/rules:
--
include /usr/share/dpatch/dpatch.make
#The upstream source don't include ./configure rule, only make
#LDFLAGS=-Wall -g
#export LDFLAGS

build: build-stamp

build-stamp: patch-stamp
dh_testdir
$(MAKE)
touch $@

clean: unpatch
dh_testdir
dh_testroot
rm -f build-stamp configure-stamp
# Add here commands to clean up after the build process.
$(MAKE) clean
dh_clean

install: build
dh_testdir
dh_testroot
dh_clean -k
dh_installdirs

# Add here commands to install the package into debian/jigzo.
cp $(CURDIR)/jigzo $(CURDIR)/debian/jigzo/usr/games
cp -r font $(CURDIR)/debian/jigzo/usr/share/jigzo
cp -r image $(CURDIR)/debian/jigzo/usr/share/jigzo
cp -r sound $(CURDIR)/debian/jigzo/usr/share/jigzo
cp -r puzzles $(CURDIR)/debian/jigzo/usr/share/jigzo
dh_install
# Build architecture-independent files here.
binary-indep: build install
# We have nothing to do by default.

# Build architecture-dependent files here.
binary-arch: build install
dh_testdir
dh_testroot
dh_installchangelogs
dh_installdocs
dh_desktop
dh_installmenu
dh_installman
dh_link
dh_strip
dh_compress
dh_fixperms
dh_installdeb
dh_shlibdeps
dh_gencontrol
dh_md5sums
dh_builddeb

binary: binary-indep binary-arch
.PHONY: build clean binary-indep binary-arch binary install configure

Sorry, I'm newbie

Thanks for advance

On Thu, Oct 2, 2008 at 3:03 PM, Elías A. M. [EMAIL PROTECTED] wrote:

 Hi,
 Somebody  know why when I build the package, show me:
 dpkg-shlibdeps: warning: debian/pack/usr/games/pack shouldn't be linked
 with libpthread.so.0 (it uses none of its symbols).

 and,

 dpkg-gencontrol: warning: unknown substitution variable ${misc:Depends}

 Those two warnings, show me. But the lintian test is ok.

 Thanks for advance,

Re: Unheeded warnings from build tools (was: Building package,)

[Paul Wise]

On Fri, Oct 3, 2008 at 7:48 AM, Ben Finney [EMAIL PROTECTED] wrote:

 The correct solution is for the warning to go away. Either this *is*
 something that needs attention, or it is not. In the former case, what
 is the problem and what is the solution? In the latter case, why is
 the warning there at all?

This won't be an issue for packages using debhelper in the future:

http://bugs.debian.org/498666

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: error when building package

[Daniel Stone]

On Fri, Jun 29, 2001 at 03:55:40AM +0200, Eric Van Buggenhaut wrote:
 On Fri, Jun 29, 2001 at 01:08:44AM +0200, Robert Millan wrote:
  Hello,
  
  when i run dpkg-buildpackage -rfakeroot to create a package, i get the following 
error:
  
  dpkg-deb: parse error, in file `debian/esms/DEBIAN/control' near line 6 package 
`esms':
   `Depends' field, missing package name, or garbage where package name expected
  dh_builddeb: command returned error code
  
  while my debian/esms/DEBIAN/control file looks correct:
  
  Package: esms
  Version: 0.8.5-1
  Section: comm
  Priority: optional
  Architecture: i386
  Depends: ,perl-base, libwww-perl
   
 
 Looks correct ??

  Depends: ${shlibs:Depends}, perl-base, libwww-perl

Definitely incorrect. What's happening is that shlibs is returning no
dependencies, or you're not running it. If you've commented out dh_shlibdeps
in your debian/rules file, then remove the ${shlibs:Depends}, section from
debian/control, otherwise comment it out and remove the ${shlibs:Depends},
section anyway.

:) d

-- 
Daniel Stone [EMAIL PROTECTED]
Nuke can NE1 help me aim nuclear weaponz? /MSG ME!!


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: error when building package

[Etienne Grossmann]

  Hello,

  I also had the problem of 

dpkg-deb: parse error, in file `debian/tmp/DEBIAN/control' near line 6 package 
`bloksi':
 `Depends' field, missing package name, or garbage where package name expected
dh_builddeb: command returned error code
make: *** [binary-indep] Error 1

  It seemed to disappear when I put the Depends line in the first
paragraph. I kept one copy of the Depends line in the 2nd paragraph;
otherwise no Depends line appears in debian/tmp/DEBIAN/control.

  This is not likely to be the right way of doing things.

  Etienne


The debian/control file :


Source: bloksi
Section: games
Priority: optional
Maintainer: Etienne Grossmann [EMAIL PROTECTED]
Standards-Version: 3.0.1
Depends: perl, libgtk-perl, libgnome-perl, libgtk-imlib-perl

Package: bloksi
Depends: perl, libgtk-perl, libgnome-perl, libgtk-imlib-perl
Architecture: all
Description: Sliding-blocks puzzle (glotski written in perl)
 Bloksi is a game of sliding-blocks puzzles in which blocks should be
 pushed around to a goal position. Nearly a clone -written in perl-
 of glotski, whose files can be read.


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: error when building package

[Paolo Molaro]

On 06/29/01 Etienne Grossmann wrote:
 dpkg-deb: parse error, in file `debian/tmp/DEBIAN/control' near line 6 package 
`bloksi':
  `Depends' field, missing package name, or garbage where package name expected
 dh_builddeb: command returned error code
 make: *** [binary-indep] Error 1
 
   It seemed to disappear when I put the Depends line in the first
 paragraph. I kept one copy of the Depends line in the 2nd paragraph;
 otherwise no Depends line appears in debian/tmp/DEBIAN/control.
 
   This is not likely to be the right way of doing things.

Read the policy and packaging manuals:
Depends belongs to the binary package stanza.
The source stanza may include Build-Depends*.

lupus

-- 
-
[EMAIL PROTECTED] debian/rules
[EMAIL PROTECTED] Monkeys do it better


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: error when building package

[Daniel Stone]

On Fri, Jun 29, 2001 at 03:55:40AM +0200, Eric Van Buggenhaut wrote:
 On Fri, Jun 29, 2001 at 01:08:44AM +0200, Robert Millan wrote:
  Hello,
  
  when i run dpkg-buildpackage -rfakeroot to create a package, i get the 
  following error:
  
  dpkg-deb: parse error, in file `debian/esms/DEBIAN/control' near line 6 
  package `esms':
   `Depends' field, missing package name, or garbage where package name 
  expected
  dh_builddeb: command returned error code
  
  while my debian/esms/DEBIAN/control file looks correct:
  
  Package: esms
  Version: 0.8.5-1
  Section: comm
  Priority: optional
  Architecture: i386
  Depends: ,perl-base, libwww-perl
   
 
 Looks correct ??

  Depends: ${shlibs:Depends}, perl-base, libwww-perl

Definitely incorrect. What's happening is that shlibs is returning no
dependencies, or you're not running it. If you've commented out dh_shlibdeps
in your debian/rules file, then remove the ${shlibs:Depends}, section from
debian/control, otherwise comment it out and remove the ${shlibs:Depends},
section anyway.

:) d

-- 
Daniel Stone [EMAIL PROTECTED]
Nuke can NE1 help me aim nuclear weaponz? /MSG ME!!

Re: error when building package

[Etienne Grossmann]

  Hello,

  I also had the problem of 

dpkg-deb: parse error, in file `debian/tmp/DEBIAN/control' near line 6 package 
`bloksi':
 `Depends' field, missing package name, or garbage where package name expected
dh_builddeb: command returned error code
make: *** [binary-indep] Error 1

  It seemed to disappear when I put the Depends line in the first
paragraph. I kept one copy of the Depends line in the 2nd paragraph;
otherwise no Depends line appears in debian/tmp/DEBIAN/control.

  This is not likely to be the right way of doing things.

  Etienne


The debian/control file :


Source: bloksi
Section: games
Priority: optional
Maintainer: Etienne Grossmann [EMAIL PROTECTED]
Standards-Version: 3.0.1
Depends: perl, libgtk-perl, libgnome-perl, libgtk-imlib-perl

Package: bloksi
Depends: perl, libgtk-perl, libgnome-perl, libgtk-imlib-perl
Architecture: all
Description: Sliding-blocks puzzle (glotski written in perl)
 Bloksi is a game of sliding-blocks puzzles in which blocks should be
 pushed around to a goal position. Nearly a clone -written in perl-
 of glotski, whose files can be read.

Re: error when building package

[Paolo Molaro]

On 06/29/01 Etienne Grossmann wrote:
 dpkg-deb: parse error, in file `debian/tmp/DEBIAN/control' near line 6 
 package `bloksi':
  `Depends' field, missing package name, or garbage where package name expected
 dh_builddeb: command returned error code
 make: *** [binary-indep] Error 1
 
   It seemed to disappear when I put the Depends line in the first
 paragraph. I kept one copy of the Depends line in the 2nd paragraph;
 otherwise no Depends line appears in debian/tmp/DEBIAN/control.
 
   This is not likely to be the right way of doing things.

Read the policy and packaging manuals:
Depends belongs to the binary package stanza.
The source stanza may include Build-Depends*.

lupus

-- 
-
[EMAIL PROTECTED] debian/rules
[EMAIL PROTECTED] Monkeys do it better

error when building package

[Robert Millan]

Hello,

when i run dpkg-buildpackage -rfakeroot to create a package, i get the following 
error:

dpkg-deb: parse error, in file `debian/esms/DEBIAN/control' near line 6 package `esms':
 `Depends' field, missing package name, or garbage where package name expected
dh_builddeb: command returned error code

while my debian/esms/DEBIAN/control file looks correct:

Package: esms
Version: 0.8.5-1
Section: comm
Priority: optional
Architecture: i386
Depends: ,perl-base, libwww-perl
Suggests: fortune
Installed-Size: 44
Maintainer: Robert Millan [EMAIL PROTECTED]
Description: [...]
[...]

and so does my debian/control file:

Source: esms
Section: comm
Priority: optional
Maintainer: Robert Millan [EMAIL PROTECTED]
Standards-Version: 3.0.1

Package: esms
Architecture: any
Depends: ${shlibs:Depends}, perl-base, libwww-perl
Suggests: fortune
Description: [...]
[...]

note that i have tried putting perl-base, libwww-perl before ${shlibs:Depends} to 
avoid that strange comma and yet didn't work.
--
Robert MillanDebian GNU user
zeratul2 wanadoo eshttp://getyouriso.org/


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: error when building package

[Eric Van Buggenhaut]

On Fri, Jun 29, 2001 at 01:08:44AM +0200, Robert Millan wrote:
 Hello,
 
 when i run dpkg-buildpackage -rfakeroot to create a package, i get the following 
error:
 
 dpkg-deb: parse error, in file `debian/esms/DEBIAN/control' near line 6 package 
`esms':
  `Depends' field, missing package name, or garbage where package name expected
 dh_builddeb: command returned error code
 
 while my debian/esms/DEBIAN/control file looks correct:
 
 Package: esms
 Version: 0.8.5-1
 Section: comm
 Priority: optional
 Architecture: i386
 Depends: ,perl-base, libwww-perl
  

Looks correct ??


 Suggests: fortune
 Installed-Size: 44
 Maintainer: Robert Millan [EMAIL PROTECTED]
 Description: [...]
 [...]
 
 and so does my debian/control file:
 
 Source: esms
 Section: comm
 Priority: optional
 Maintainer: Robert Millan [EMAIL PROTECTED]
 Standards-Version: 3.0.1
 
 Package: esms
 Architecture: any
 Depends: ${shlibs:Depends}, perl-base, libwww-perl
 Suggests: fortune
 Description: [...]
 [...]
 
 note that i have tried putting perl-base, libwww-perl before ${shlibs:Depends} to 
avoid that strange comma and yet didn't work.
 --
 Robert MillanDebian GNU user
 zeratul2 wanadoo eshttp://getyouriso.org/
 
 
 --  
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 

-- 
Eric VAN BUGGENHAUT

[EMAIL PROTECTED]


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: error when building package

[Eric Van Buggenhaut]

On Fri, Jun 29, 2001 at 01:08:44AM +0200, Robert Millan wrote:
 Hello,
 
 when i run dpkg-buildpackage -rfakeroot to create a package, i get the 
 following error:
 
 dpkg-deb: parse error, in file `debian/esms/DEBIAN/control' near line 6 
 package `esms':
  `Depends' field, missing package name, or garbage where package name expected
 dh_builddeb: command returned error code
 
 while my debian/esms/DEBIAN/control file looks correct:
 
 Package: esms
 Version: 0.8.5-1
 Section: comm
 Priority: optional
 Architecture: i386
 Depends: ,perl-base, libwww-perl
  

Looks correct ??


 Suggests: fortune
 Installed-Size: 44
 Maintainer: Robert Millan [EMAIL PROTECTED]
 Description: [...]
 [...]
 
 and so does my debian/control file:
 
 Source: esms
 Section: comm
 Priority: optional
 Maintainer: Robert Millan [EMAIL PROTECTED]
 Standards-Version: 3.0.1
 
 Package: esms
 Architecture: any
 Depends: ${shlibs:Depends}, perl-base, libwww-perl
 Suggests: fortune
 Description: [...]
 [...]
 
 note that i have tried putting perl-base, libwww-perl before 
 ${shlibs:Depends} to avoid that strange comma and yet didn't work.
 --
 Robert MillanDebian GNU user
 zeratul2 wanadoo eshttp://getyouriso.org/
 
 
 --  
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 

-- 
Eric VAN BUGGENHAUT

[EMAIL PROTECTED]

RE: GPG problem when building package

[Sean 'Shaleh' Perry]

On 20-Jul-2000 John O Sullivan wrote:
 Hi,
 I've run into a problem near the end of building a package.
 When I run dpkg-buildpackage -rfakeroot I'm not asked for my GPG
 passphrase and I get this error message:
 gpg: skipped `John O Sullivan [EMAIL PROTECTED]': secret key not available
 gpg: [stdin]: clearsign failed: secret key not available
 
 The .deb, .diff.gz and other files are created though.
 I know nearly nothing about gpg so any help would be appreciated.
 

gpg is passed the name from the changelog entry.  If this is not the name on
your key, it wont work.

geisha [~/gdm2] $ gpg --edit-key [EMAIL PROTECTED]
Secret key is available.

pub  1024D/9EE16F1B  created: 1999-10-12 expires: never  trust: -/u
sub  2048g/5BF5DA52  created: 1999-10-12 expires: never 
(1)  Sean 'Shaleh' Perry [EMAIL PROTECTED]

note it lists my name as Sean 'Shaleh' Perry, that has to be what is in the
changelog.  you can alias one name to another.  All of this is explained on the
gnupg.org web site.

RE: GPG problem when building package

[John O Sullivan]

Thanks, that was the problem, 
John O Sullivan != John O'Sullivan

johno

Sean 'Shaleh' Perry writes:
  gpg is passed the name from the changelog entry.  If this is not the name on
  your key, it wont work.
  
  geisha [~/gdm2] $ gpg --edit-key [EMAIL PROTECTED]
  Secret key is available.
  
  pub  1024D/9EE16F1B  created: 1999-10-12 expires: never  trust: -/u
  sub  2048g/5BF5DA52  created: 1999-10-12 expires: never 
  (1)  Sean 'Shaleh' Perry [EMAIL PROTECTED]
  
  note it lists my name as Sean 'Shaleh' Perry, that has to be what is in the
  changelog.  you can alias one name to another.  All of this is explained on 
  the
  gnupg.org web site.

GPG problem when building package

[John O Sullivan]

Hi,
I've run into a problem near the end of building a package.
When I run dpkg-buildpackage -rfakeroot I'm not asked for my GPG
passphrase and I get this error message:
gpg: skipped `John O Sullivan [EMAIL PROTECTED]': secret key not available
gpg: [stdin]: clearsign failed: secret key not available

The .deb, .diff.gz and other files are created though.
I know nearly nothing about gpg so any help would be appreciated.

thanks,
johno

Re: Building package with gpg

[Christian Surchi]

On 18-Oct-99 Gergely Madarasz wrote:

 Remove the rfc1991 line from your .gnupg/options

What does the line mean?

---
   Christian Surchi, [EMAIL PROTECTED], www.firenze.linux.it/~csurchi
  Debian GNU/Linux User  -  www.debian.org
  PGP fingerprint = 05 CE 0B BE BF FC B6 14  53 CA C7 8E AE 3A F2 6A
  GPG fingerprint = D1E2 9A9D 1712 0E94 8671  834E 0CFF 30E1 2625 7B68

Building package with gpg

[Ben Darnell]

I am trying to build my first package since switching to gpg, but it
isn't working.  It appears to sign it OK, but gpg --verify says it's a
bad signature.  gpg works in mutt (I think; I'm signing this message to
be sure).  I've attached the .changes file (built with dpkg-buildpackage
-rfakeroot -sgpg -pgpg).  I'm using dpkg-dev 1.4.1.16 and gnupg 1.0.0-1.

-Ben

-- 
Ben Darnell  [EMAIL PROTECTED]
http://www4.ncsu.edu/~bgdarnel/thoughtstream/

-BEGIN PGP SIGNED MESSAGE-

Format: 1.6
Date: Tue, 12 Oct 1999 12:49:56 -0400
Source: pilot-link
Binary: libpisock3 pilot-link-tcl pilot-link-perl pilot-link libpisock-dev
Architecture: source i386
Version: 0.9.3-2
Distribution: unstable
Urgency: low
Maintainer: Ben Darnell [EMAIL PROTECTED]
Description: 
 libpisock-dev - static libraries for communicating with a Pilot PDA.
 libpisock3 - Libraries for communicating with a Pilot PDA.
 pilot-link - Tools to communicate with a 3COM Pilot PDA over a serial port.
 pilot-link-perl - Perl tools to communicate with a 3COM Pilot PDA over a 
serial por
 pilot-link-tcl - TCL tools to communicate with a 3COM Pilot PDA over a serial 
port
Changes: 
 pilot-link (0.9.3-2) unstable; urgency=low
 .
   * Clean up some lintian errors
Files: 
 7616e0c236b8afcfe74ea7684ad73b7a 617 otherosfs extra pilot-link_0.9.3-2.dsc
 3760a1c0607aa96dbb2e7c9f99b97390 7626 otherosfs extra 
pilot-link_0.9.3-2.diff.gz
 815c223f019c70876833650397c7ef0c 40388 libs extra libpisock3_0.9.3-2_i386.deb
 82fbbd0b6e919bc18f000830dc5147fc 79198 devel extra 
libpisock-dev_0.9.3-2_i386.deb
 9e5ca337d2db9172393d9626cf30b9c3 62294 devel extra 
pilot-link-perl_0.9.3-2_i386.deb
 b8a4e19e01a05f4d9cfa5504de91079f 34160 devel extra 
pilot-link-tcl_0.9.3-2_i386.deb
 46d98425fc6af453b2d98872ed7cafd7 185660 otherosfs extra 
pilot-link_0.9.3-2_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE4C1+lRSRBmB8G5QkRAsyvAJ0Sn/hmSzVkwi6KhbE8fha805BQvQCePD0g
NvTR/Feqq/lrGnp6WDwtil8=
=md4p
-END PGP SIGNATURE-


pgpmwPtRovz3O.pgp
Description: PGP signature

Re: Building package with gpg

[Gergely Madarasz]

On Mon, 18 Oct 1999, Ben Darnell wrote:

 I am trying to build my first package since switching to gpg, but it
 isn't working.  It appears to sign it OK, but gpg --verify says it's a
 bad signature.  gpg works in mutt (I think; I'm signing this message to
 be sure).  I've attached the .changes file (built with dpkg-buildpackage
 -rfakeroot -sgpg -pgpg).  I'm using dpkg-dev 1.4.1.16 and gnupg 1.0.0-1.

Remove the rfc1991 line from your .gnupg/options

-- 
Madarasz Gergely   [EMAIL PROTECTED] [EMAIL PROTECTED]
  It's practically impossible to look at a penguin and feel angry.
  Egy pingvinre gyakorlatilag lehetetlen haragosan nezni.
HuLUG: http://mlf.linux.rulez.org/