Hi Gunnar,
On 19.10.2016 18:33, Gunnar Wolf wrote:
> So... Does this sound sensible? Were you in my place, would you submit
> this package to ftp-masters? What would you change about it?
What you describe sounds quite sensible to me, though I haven't
actually looked at the repository.
What's
@@ -0,0 +1,19 @@
+Description: Unset Cmake variables on configuration change
+ Previously they have been set to arbitrary values, but that confuses
+ recent versions of cmake.
+
+Author: Andreas Cadhalpun andreas.cadhal...@googlemail.com
+Bug-Debian: https://bugs.debian.org/788559
+Last-Update: 2015-07
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
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 Thomas,
On 13.07.2014 10:41, Thomas Moulard wrote:
I recently uploaded a binary incompatible new version of the ViSP C++ library.
We have in testing a package libvisp2.8_2.8.0-5.1 and in unstable a
package libvisp2.9_2.9.0-2
So far, so good. The library changed it's SOVERSION and thus a
5 matches
Mail list logo
