Re: inetutils upset messages

2014-04-09 Thread Achim Gratz
Christopher Faylor writes: > On Wed, Apr 09, 2014 at 11:28:25PM +0200, Achim Gratz wrote: >>It appears that the new setup.ini is generated before any file removals >>have happened, but after the copies have been done. > > No, that is not right. The setup.ini is created last. Then I have no idea h

Re: inetutils upset messages

2014-04-09 Thread Christopher Faylor
On Thu, Apr 10, 2014 at 12:32:59AM +0200, Achim Gratz wrote: >Achim Gratz writes: >> Christopher Faylor writes: >>> Nevermind. Stupid coding error. >> >> It appears that the new setup.ini is generated before any file removals >> have happened, but after the copies have been done. I don't know if

Re: inetutils upset messages

2014-04-09 Thread Christopher Faylor
On Wed, Apr 09, 2014 at 11:28:25PM +0200, Achim Gratz wrote: >Christopher Faylor writes: >> Nevermind. Stupid coding error. > >It appears that the new setup.ini is generated before any file removals >have happened, but after the copies have been done. No, that is not right. The setup.ini is crea

Re: inetutils upset messages

2014-04-09 Thread Achim Gratz
Achim Gratz writes: > Christopher Faylor writes: >> Nevermind. Stupid coding error. > > It appears that the new setup.ini is generated before any file removals > have happened, but after the copies have been done. I don't know if > that will produce yet another error from upset (so far there are

Re: inetutils upset messages

2014-04-09 Thread Achim Gratz
Christopher Faylor writes: > Nevermind. Stupid coding error. It appears that the new setup.ini is generated before any file removals have happened, but after the copies have been done. I don't know if that will produce yet another error from upset (so far there are none), but since I was trying

Re: 64-bit: Missing perl modules

2014-04-09 Thread Achim Gratz
Yaakov (Cygwin/X) writes: > Yes, we do want to have packages for all Perl modules required by > other packages. Telling users "oh, if you want to make this Cygwin > package work, go install the modules from CPAN" is not a viable > solution. Thanks, Yaakov. The packaging issue introduced by the o

Re: 64-bit: Missing perl modules

2014-04-09 Thread Reini Urban
On Tue, Apr 8, 2014 at 4:27 PM, Achim Gratz wrote: > Reini Urban writes: >> Only if you register each and every user module with the system. >> But we don't want that. > > Wait, weren't we talking about vendor-perl, possibly site-perl? These > two locations are already "registered with the system"