Bug#851166: nmu: forge_0.9.2-2 [RC]

2017-01-19 Thread Ghislain Vaillant 
Unless I should just make a standard upload? The thing is that I have
nothing else to add to the current state of the packaging besides:

"Rebuild with fixed glm"

Which is what I thought binNMUs were for? I am not very familiar with
them as you can probably tell.

Cheers,
Ghis


On Wed, 2017-01-18 at 22:20 +, Ghislain Vaillant wrote:
> Yes, because glm is fixed now.
> 
> Le 18 janv. 2017 9:54 PM, "Emilio Pozuelo Monfort"  a écrit 
> :
> On 14/01/17 20:32, Ghislain Vaillant wrote:
> > I forgot to mention that this NMU would fix the current RC affecting
> > forge. The FTBFS was due to a bug in the CMake detection of the glm
> > library, which I have fixed since.
> 
> I'm not sure I understand. If there is a FTBFS, wouldn't the binNMU fail to
> build? If not, why not?
> 
> Do you actually want us to retry the failed builds in [1] ?
> 
> [1] https://buildd.debian.org/status/package.php?p=forge
> 
> Cheers,
> Emilio
>

Bug#851166: nmu: forge_0.9.2-2 [RC]

2017-01-18 Thread Ghislain Vaillant 
Yes, because glm is fixed now.

Le 18 janv. 2017 9:54 PM, "Emilio Pozuelo Monfort"  a
écrit :

On 14/01/17 20:32, Ghislain Vaillant wrote:
> I forgot to mention that this NMU would fix the current RC affecting
> forge. The FTBFS was due to a bug in the CMake detection of the glm
> library, which I have fixed since.

I'm not sure I understand. If there is a FTBFS, wouldn't the binNMU fail to
build? If not, why not?

Do you actually want us to retry the failed builds in [1] ?

[1] https://buildd.debian.org/status/package.php?p=forge

Cheers,
Emilio

Bug#851166: nmu: forge_0.9.2-2 [RC]

2017-01-18 Thread Emilio Pozuelo Monfort 
On 14/01/17 20:32, Ghislain Vaillant wrote:
> I forgot to mention that this NMU would fix the current RC affecting
> forge. The FTBFS was due to a bug in the CMake detection of the glm
> library, which I have fixed since.

I'm not sure I understand. If there is a FTBFS, wouldn't the binNMU fail to
build? If not, why not?

Do you actually want us to retry the failed builds in [1] ?

[1] https://buildd.debian.org/status/package.php?p=forge

Cheers,
Emilio

Bug#851166: nmu: forge_0.9.2-2 [RC]

2017-01-14 Thread Ghislain Vaillant 
On Thu, 12 Jan 2017 16:06:31 + Ghislain Antony Vaillant 
 wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> nmu forge_0.9.2-2 . ANY . unstable . -m "Rebuild with fixed glm"
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (900, 'testing'), (300, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.8.0-2-amd64 (SMP w/8 CPU cores)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)

I forgot to mention that this NMU would fix the current RC affecting
forge. The FTBFS was due to a bug in the CMake detection of the glm
library, which I have fixed since.

Ghis

Bug#851166: nmu: forge_0.9.2-2

2017-01-12 Thread Ghislain Antony Vaillant 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

nmu forge_0.9.2-2 . ANY . unstable . -m "Rebuild with fixed glm"

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (300, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)