Re: [ACTION REQUIRED] ARCH=noarch uploads with cygport 0.22.0 (+ python-feedparser)

2016-06-08 Thread Jari Aalto
2016-06-07 11:23 Jari Aalto : | | ... maintainers MUST email a list of their package(s) which qualify | | as noarch AND are already marked ARCH=noarch ... | | Checked. All can be moved to noarch (...) Add this to the noarch list too: python-feedparser Jari | Packages: | | Jari Aalto

Re: [ITP] libsass v3.3.6

2016-06-08 Thread Achim Gratz
Marcos Vives Del Sol writes: > 2016-06-08 7:46 GMT+02:00 Achim Gratz: >> They didn't forget anything, you are just not using a release tarball. >> In that case you are expected to either build from a proper Git checkout >> or run the release preparations yourself before configure. > I am compiling

Re: [ACTION REQUIRED] ARCH=noarch uploads with cygport 0.22.0

2016-06-08 Thread Achim Gratz
Achim Gratz writes: > Yaakov Selkowitz writes: >> The attached list contains packages which on the surface appear to be >> noarch but haven't been moved yet. PLEASE **DOUBLE-CHECK** your >> packages on this list, and if your package qualifies, proceed as >> above. If not, please state why for futu

Re: [ITP] libsass v3.3.6

2016-06-08 Thread Marcos Vives Del Sol
2016-06-08 7:46 GMT+02:00 Achim Gratz: > They didn't forget anything, you are just not using a release tarball. > In that case you are expected to either build from a proper Git checkout > or run the release preparations yourself before configure. I am compiling a release tarball, as I've already s