Hi Bernhard,
Le dimanche, 14 décembre 2014, 15.47:47 Bernhard Übelacker a écrit :
> So probably the solution could be only these 2 steps?
>
> - to rebuild package nsis-common with the current g++-mingw-w64-i686
> package
>
> - rebuild win32-loader with the newly built nsis-common package
> insta
Le lundi, 15 décembre 2014, 19.20:07 Adam D. Barratt a écrit :
> On Mon, 2014-12-15 at 10:09 +0100, Didier 'OdyX' Raboud wrote:
> > @Release Team, could we please schedule binNMUs for nsis ?
> >
> > nmu nsis_2.46-9 . ALL . -m "Rebuild with gcc-mingw-w64 14 to ensure
> > that NSISdl.dll doe
On Mon, 2014-12-15 at 10:09 +0100, Didier 'OdyX' Raboud wrote:
> @Release Team, could we please schedule binNMUs for nsis ?
>
> nmu nsis_2.46-9 . ALL . -m "Rebuild with gcc-mingw-w64 14 to ensure
> that NSISdl.dll doesn't depend on a shared libwinpthread-1"
Done.
Regards,
Adam
--
To U
Processing control commands:
> clone -1 -2
Bug #772898 [win32-loader] win32-loader testing and newer fails with TRANSLATE
error
Bug 772898 cloned as bug 773167
> retitle -2 nmu: nsis_2.46-9
Bug #773167 [win32-loader] win32-loader testing and newer fails with TRANSLATE
error
Changed Bug title to
Control: clone -1 -2
Control: retitle -2 nmu: nsis_2.46-9
Control: user -2 release.debian@packages.debian.org
Control: usertag -2 +binnmu
(Release Team, please see below :) )
Hi Bernhard & Cyril,
Many thanks for the detailed analysis!
Le dimanche, 14 décembre 2014, 15.47:47 Bernhard Übelack
Hello,
just some additions.
Looks similar to bug #654380. (There mingw defaulted to produce dlls
depending also on some other mingw dlls)
There the upstream bug report [2] mentions that plugins "must not depend
on a shared libgcc".
So I assume that the plugins "must not depend on a shared libwin
Bernhard Übelacker (2014-12-12):
> Hello,
> probably I have found something more.
>
> I tested in a VM with a more recent windows version, therefore I cannot
> sure that this is the reason you saw (having to run win32-loader with
> compatibility set to windows 7 on a windows 8.1 32bit).
>
> I us
Hello,
probably I have found something more.
I tested in a VM with a more recent windows version, therefore I cannot
sure that this is the reason you saw (having to run win32-loader with
compatibility set to windows 7 on a windows 8.1 32bit).
I used the version from [1].
Because you already hint
Hi all,
Le vendredi, 12 décembre 2014 10.03:10, vous avez écrit :
> Le jeudi, 11 décembre 2014, 17.15:49 Jimmy Kaplowitz a écrit :
> > I got this error:
> >
> > "Error:
> > http://d-i.debian.org/daily-images/amd64/daily//MD5SUMS/TRANSLATE";
>
> This error is an artifact of the failure of the win
Processing control commands:
> tags -1 +confirmed
Bug #772898 [win32-loader] win32-loader testing and newer fails with TRANSLATE
error
Added tag(s) confirmed.
--
772898: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problem
Processing control commands:
> severity -1 serious
Bug #772898 [win32-loader] win32-loader testing and newer fails with TRANSLATE
error
Severity set to 'serious' from 'normal'
--
772898: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772898
Debian Bug Tracking System
Contact ow...@bugs.debian
control: severity -1 serious
thanks
Hi Jimmy,
thanks for your bug report!
On Freitag, 12. Dezember 2014, Jimmy Kaplowitz wrote:
> or daily d-i. Here is one of the paths I tried with both the testing and
> unstable versions, and the resulting error:
> "Error:
> http://d-i.debian.org/daily-images/
Package: win32-loader
Version: 0.7.5
Hi,
I just got a new laptop preinstalled with Windows 7 Pro, and naturally wanted
to install Debian via win32-loader. I tried several times, with the testing and
unstable versions of win32-loader, and picking either stable or daily d-i. Here
is one of the path
13 matches
Mail list logo
