Which packages are these? It's probably a bug in the package source, in
that it's coded in such a way that bin-nmu's aren't possible. There're
a bunch of packages like that. (ie, a Depends: otherpkg (= myver) line)
In my case it's esound-common, which in turn makes the entire gnome tree not
On Saturday 15 September 2001 07:29, you wrote:
In my case it's esound-common, which in turn makes the entire gnome tree
not installable.
Most of the esound packages have a 'esound-common (= ${Source-Version})'
dependency in debian/control. Is there any generic solution for the problem?
On Sat, Sep 15, 2001 at 07:41:21AM +0200, Gerhard Tonn wrote:
On Saturday 15 September 2001 07:29, you wrote:
In my case it's esound-common, which in turn makes the entire gnome tree
not installable.
Most of the esound packages have a 'esound-common (= ${Source-Version})'
dependency in
Package: debhelper
Version: 3.0.44
Severity: normal
On Sat, 15 Sep 2001, Matt Zimmerman wrote:
Most of the esound packages have a 'esound-common (= ${Source-Version})'
dependency in debian/control. Is there any generic solution for the problem?
You could manually tweak debian/substvars
Simon Richter wrote:
Hrm, I just tried to build a package using
DH_OPTIONS=--dpkg-gencontrol-params=-v0.1-1.0.1 dpkg-buildpackage -B
In principle this could work, however current debhelper treats
--dpkg-gencontrol-params as equivalent to -u in
Debian::Debhelper::Dh_Getopt, so the -v
Hi,
I have done some binary NMUs for s390 in order to fix bugs caused by previous
compiler bugs.
I experience now the following problem:
The architecture dependent package created by the NMU have a 0.1 version, the
architecture independent package compiled from the same source package don't
On Fri, Sep 14, 2001 at 05:49:54PM +0200, Gerhard Tonn wrote:
I have done some binary NMUs for s390 in order to fix bugs caused by previous
compiler bugs.
I experience now the following problem:
The architecture dependent package created by the NMU have a 0.1 version, the
architecture
On Sat, Sep 15, 2001 at 02:58:30AM +1000, Anthony Towns wrote:
Which packages are these? It's probably a bug in the package source, in
that it's coded in such a way that bin-nmu's aren't possible. There're
a bunch of packages like that. (ie, a Depends: otherpkg (= myver) line)
This problem
8 matches
Mail list logo