On 2019-12-29 01:16:01 -0500, Joe Nahmias wrote:
> On 12/27/2019 6:23 PM, Vincent Lefevre wrote:
> > On 2019-12-27 19:49:46 +, Joseph Nahmias wrote:
> > > On Fri, Dec 27, 2019 at 07:27:42PM +, Joseph Nahmias wrote:
> > > > The attached patch works around the issue until that is fixed.
> >
On 12/27/2019 6:23 PM, Vincent Lefevre wrote:
On 2019-12-27 19:49:46 +, Joseph Nahmias wrote:
On Fri, Dec 27, 2019 at 07:27:42PM +, Joseph Nahmias wrote:
The attached patch works around the issue until that is fixed.
Of course, I forgot this patch... Take 2.
Wouldn't the use of
On 2019-12-27 19:49:46 +, Joseph Nahmias wrote:
> On Fri, Dec 27, 2019 at 07:27:42PM +, Joseph Nahmias wrote:
> > The attached patch works around the issue until that is fixed.
>
> Of course, I forgot this patch... Take 2.
Wouldn't the use of wildcards be a security issue?
+ ln -s
On Fri, Dec 27, 2019 at 07:27:42PM +, Joseph Nahmias wrote:
> The attached patch works around the issue until that is fixed.
Of course, I forgot this patch... Take 2.
--Joe
diff -Nru win-iconv-0.0.8/debian/changelog win-iconv-0.0.8/debian/changelog
--- win-iconv-0.0.8/debian/changelog
package win-iconv
tags 921904 + patch
thanks
On Fri, Dec 27, 2019 at 06:19:41PM +, Joseph Nahmias wrote:
> Hello,
>
> On Mon, Mar 18, 2019 at 10:12:55AM -0400, Daniel Kahn Gillmor wrote:
> >
> > If anyone else needs win-iconv in debian, please speak up!
> >
> > Otherwise i'll probably move
Hello,
On Mon, Mar 18, 2019 at 10:12:55AM -0400, Daniel Kahn Gillmor wrote:
> On Mon 2019-03-18 10:55:44 +0100, Tim Rühsen wrote:
> > Libiconv 1.15 itself from tarball.
> >
> > If you are interested in the details, have a look at our CI Dockerfile
> > where we build/install the dependencies
On Mon 2019-03-18 10:55:44 +0100, Tim Rühsen wrote:
> Libiconv 1.15 itself from tarball.
>
> If you are interested in the details, have a look at our CI Dockerfile
> where we build/install the dependencies needed for testing:
>
>
On 3/17/19 11:11 PM, Daniel Kahn Gillmor wrote:
> On Sun 2019-03-17 13:14:54 +0100, Tim Rühsen wrote:
>> Fixed it by building my own libiconv on MinGW systems. It really is
>> straight forward and possibly no extra Debian package is needed.
>
> Thanks for the feedback, Tim. For your fix, are you
On Sun 2019-03-17 13:14:54 +0100, Tim Rühsen wrote:
> Fixed it by building my own libiconv on MinGW systems. It really is
> straight forward and possibly no extra Debian package is needed.
Thanks for the feedback, Tim. For your fix, are you building libiconv
itself, or win-iconv for MinGW
Fixed it by building my own libiconv on MinGW systems. It really is
straight forward and possibly no extra Debian package is needed.
Regards, Tim
On Sat, 16 Mar 2019 21:02:26 +0100 =?UTF-8?Q?Tim_R=c3=bchsen?=
wrote:
> Please do not remove this package, the first CI builds (MinGW cross
> builds)
Please do not remove this package, the first CI builds (MinGW cross
builds) already break (GNU Wget / Wget2).
Well, it's already gone from buster... please add it back or provide a
another way to convert charsets within cross-compiled Windows executables.
Regards, Tim
signature.asc
Processing control commands:
> tags 921904 + help
Bug #921904 [src:win-iconv] win-iconv: FTBFS (wine: chdir to
/tmp/wine-I6miLw/server-29-3583b06 : No such file or directory)
Added tag(s) help.
--
921904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921904
Debian Bug Tracking System
Control: tags 921904 + help
On Sat 2019-02-09 23:50:03 +, Santiago Vila wrote:
> Package: src:win-iconv
> Version: 0.0.8-2
> Severity: serious
> Tags: ftbfs
>
> Dear maintainer:
>
> I tried to build this package in buster but it failed:
>
>
Package: src:win-iconv
Version: 0.0.8-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep
14 matches
Mail list logo
