Daniel Lintott dan...@serverb.co.uk wrote:
On Sun, Nov 16, 2014 at 02:39:15PM +0100, Andreas Metzler wrote:
Daniel Lintott dan...@serverb.co.uk wrote:
I have a package which is split into two sources (a server and
gui). The server version should match the gui version (upstream
version) at all
On Sun, Nov 16, 2014 at 02:39:15PM +0100, Andreas Metzler wrote:
Daniel Lintott dan...@serverb.co.uk wrote:
I have a package which is split into two sources (a server and gui). The
server version should match the gui version (upstream version) at all times.
Because of this when I'm
Daniel Lintott dan...@serverb.co.uk wrote:
I have a package which is split into two sources (a server and gui). The
server version should match the gui version (upstream version) at all times.
Because of this when I'm creating the meta-package that will depend on
both the gui and server,
On 12/11/14 22:40, Andreas Cadhalpun wrote:
[...]
You require the exact upstream version (1.1).
This can't work, because there will always be the Debian revision added
(1.1-1~exp1).
I had a suspicion that this was why, but wasn't sure.
What should work better is '=
On 12/11/14 23:32, Henrique de Moraes Holschuh wrote:
On Wed, 12 Nov 2014, Roger Light wrote:
Could you try ${binary:Version} instead?
(= ${binary:Version}) can break binNMUs. Be careful.
Indeed, I am keen to try and avoid any breakages like that. I also don't
think the above would work
On Wed, 12 Nov 2014, Henrique de Moraes Holschuh wrote:
On Wed, 12 Nov 2014, Roger Light wrote:
Could you try ${binary:Version} instead?
(= ${binary:Version}) can break binNMUs. Be careful.
binNMUs will cause a few of the binary packages to have a different
debian revision than the rest of
binNMUs will cause a few of the binary packages to have a different
debian revision than the rest of the binary packages and the source
packages.
We have a lintian check for this, I think.
Is it not-binnmuable-all-depends-any? I should've remembered that one,
because I use the fix that is
Hi Daniel,
On 13.11.2014 11:29, Daniel Lintott wrote:
On 12/11/14 22:40, Andreas Cadhalpun wrote:
What should work better is '= ${source:Upstream-Version}'.
However, that is not enough to guarantee that the upstream versions
always match. One could then have e.g.:
gns3= 1.1-1
gns3-gui
I have a package which is split into two sources (a server and gui). The
server version should match the gui version (upstream version) at all times.
Because of this when I'm creating the meta-package that will depend on
both the gui and server, should be versioned to to be the same upstream
Hi Daniel,
On 12.11.2014 22:30, Daniel Lintott wrote:
I have a package which is split into two sources (a server and gui). The
server version should match the gui version (upstream version) at all times.
Because of this when I'm creating the meta-package that will depend on
both the gui and
Hi Daniel,
Could you try ${binary:Version} instead?
Cheers,
Roger
On Wed, Nov 12, 2014 at 9:30 PM, Daniel Lintott dan...@serverb.co.uk wrote:
I have a package which is split into two sources (a server and gui). The
server version should match the gui version (upstream version) at all times.
On Wed, 12 Nov 2014, Roger Light wrote:
Could you try ${binary:Version} instead?
(= ${binary:Version}) can break binNMUs. Be careful.
--
One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows
12 matches
Mail list logo
