Re: [PATCH setup 0/3] Setup replacement for incver_ifdep

2015-11-23 Thread Achim Gratz
Jon Turney writes: > So, this is actually quite straightforward to write, and > /etc/postinstall/0p_update-info-dir.sh becomes the attached. > >>> Can this be relied on for all possible file systems? >> >> Not on FAT. But then again, FAT is not really a filesystem, rather just >> a failed try. > >

Re: [PATCH setup 0/3] Setup replacement for incver_ifdep

2015-11-23 Thread Jon Turney
On 15/10/2015 19:01, Achim Gratz wrote: Jon Turney writes: I still don't think the triggers should be implemented or at least not in the way you've been proposing. Can you explain the reason why? Triggers need to be coordinated among packages and we currently don't have an infrastructure for

Re: [PATCH setup 0/3] Setup replacement for incver_ifdep

2015-11-23 Thread Jon Turney
On 20/10/2015 11:21, Corinna Vinschen wrote: On Oct 19 19:21, Achim Gratz wrote: Corinna Vinschen writes: I agree. Actually, considering that the info files are stored in just a single well-known directory, /usr/share/info(*), and further considering that updated files are rewritten when overw

Re: Python not reading result from bash command

2015-11-23 Thread cyg Simple
On 11/23/2015 4:25 AM, Aaron Schneider wrote: > >> Subject: Re: Python not reading result from bash command >> >> what is adb ? >> >> I suspect it is mainly pty communication (or lack of) between >> cygwin and not cygwin programs. >> See >> https://github.co

RE: Python not reading result from bash command

2015-11-23 Thread Aaron Schneider
> Subject: Re: Python not reading result from bash command > > what is adb ? > > I suspect it is mainly pty communication (or lack of) between > cygwin and not cygwin programs. > See > https://github.com/mintty/mintty/issues/56 adb is the Android Debugging

Re: Python not reading result from bash command

2015-11-23 Thread Marco Atzeri
On 23/11/2015 10:04, Aaron Schneider wrote: Subject: Python not reading result from bash command Trying to read an argument as string, however doesn't work on python for cygwin. Tested on Python 3.5.0 (32-bit) from Python Software Foundation and works perfectly. test.py: import datetime imp

RE: Python not reading result from bash command

2015-11-23 Thread Aaron Schneider
> Subject: Python not reading result from bash command > > Trying to read an argument as string, however doesn't work on python for > cygwin. Tested on Python 3.5.0 (32-bit) from Python Software Foundation and > works perfectly. > > test.py: > import datetime > import sys > my_date = str(sys.argv

Python not reading result from bash command

2015-11-23 Thread Aaron Schneider
Trying to read an argument as string, however doesn't work on python for cygwin. Tested on Python 3.5.0 (32-bit) from Python Software Foundation and works perfectly. test.py: import datetime import sys my_date = str(sys.argv[1]) temp_date = datetime.datetime.strptime(some_date, "%Y%m%d%H%M%S")