The extension wasn't really part of the filename in those days. So aux.c and aux.hs is interpreted as aux. The funny thing is that Microsoft soon recognized how bad it was and added a flag to make it unix-like (\dev\nul etc) and free the names in dos 2.0, but the default stayed as it was. Niklas ----- Ursprungligt meddelande ----- Från: "Frerich Raabe" Skickat: ‎2014-‎06-‎16 13:15 Till: "haskell-cafe@haskell.org" Ämne: Re: [Haskell-cafe] Uploading to hackage fails: bad file names intarball Hi, There are a couple more special files, most (all?) of which are documented at http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).as... That page also says "Also avoid these names followed immediately by an extension; for example, NUL.txt is not recommended." and I suspect that it may be this recommendation based on which the error is raised. "NUL.txt" as well as "Aux.hs" are valid file names though. There is no file named 'AUX' though, and "Aux.hs" is a valid filename. On 2014-06-16 11:45, Niklas Larsson wrote:

Hi!

For extremely ancient and cludgy reasons AUX isn't a valid filename on windows, it's a DOS device. The other similarly reserved name are CON, PRN and NUL.

Niklas

----- Ursprungligt meddelande ----- Från: "Arie Peterson" Skickat: ‎2014-‎06-‎16 10:45 Till: "haskell-cafe@haskell.org" Ämne: [Haskell-cafe] Uploading to hackage fails: bad file names in tarball

Since some time, I have been unable to upload packages to Hackage, via either the 'cabal upload' command, or using the web form.

The error message it gives is this:

==== ✂ ==== Hackage username: AriePeterson Hackage password: Uploading dist/np-linear-0.1.1.1.tar.gz... Error: dist/np-linear-0.1.1.1.tar.gz: 400 Bad Request Error: Invalid package

Invalid windows file name in tar archive: "np-linear-0.1.1.1\\src\\Aux.hs". For portability, hackage requires that file names be valid on both Unix and Windows systems, and not refer outside of the tarball. ==== ✂ ====

The tarball is created by 'cabal sdist': cabal-install version 1.18.0.2 using version 1.18.1.1 of the Cabal library.

I also installed the newest cabal-install, on another machine, but this did not help (same error).

I also tried to create a tarball by hand, using 'tar --format=ustar', but this again resulted in the same error message.

By the way, I'm on linux, not Windows, so it is not clear how the backslashes get in the file names.

What could be going on?

_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

-- Frerich Raabe - raabe@froglogic.com www.froglogic.com - Multi-Platform GUI Testing _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe