Bug#817274: python-gevent: FTBFS: can't read debian/python-gevent-doc/...

2016-03-09 Thread GCS
On Thu, Mar 10, 2016 at 4:47 AM, Aaron M. Ucko  wrote:
> "László Böszörményi (GCS)"  writes:
>> Then I have to update the changelog closing the bugreport and rebuild
>> the package.  :)
>
> I do see how that could get a little frustrating.  It's too bad there's
> no lightweight way for you to publicly indicate awareness of a build
> failure short of filing a report yourself.
 I can send you an email in advance.

>>  No problem, next time I should wait more on you to file the bugreport.
>
> You know, you could also perform more sanity checks *before*
> uploading... ;-)
 My machine is so old that I'm happy it works and compiles packages
once in a reasonable time. But sure, there's ccache and I should have
realized documentation is built in the indep targets only - that
buildds don't execute.
It was degrading when I've patched a problem in an upstream source and
started compiling. While it was going, I've sent the patch upstream.
Some time later I got the answer, he patched the source, compiled and
tested the issue which is fine now. My box was still compiling that
source... :-/ I will be able to buy a new one this summer or autumn.
You are still right, I should do more sanity checks before uploading.

Offtopic: as I know, DebConf'17 will be close to you. Any plans to attend it?

Regards,
Laszlo/GCS



Bug#817274: python-gevent: FTBFS: can't read debian/python-gevent-doc/...

2016-03-09 Thread Aaron M. Ucko
"László Böszörményi (GCS)"  writes:

> Then I have to update the changelog closing the bugreport and rebuild
> the package.  :)

I do see how that could get a little frustrating.  It's too bad there's
no lightweight way for you to publicly indicate awareness of a build
failure short of filing a report yourself.

>  No problem, next time I should wait more on you to file the bugreport.

You know, you could also perform more sanity checks *before*
uploading... ;-)

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu



Bug#817274: python-gevent: FTBFS: can't read debian/python-gevent-doc/...

2016-03-09 Thread GCS
On Wed, Mar 9, 2016 at 11:30 PM, Aaron M. Ucko  wrote:
> "László Böszörményi (GCS)"  writes:
> I prefer to follow this whole procedure fairly frequently so that I
> don't have too many reports to file at any one time.
 OK, it just doesn't let the maintainer fix the issue. When I'm about
to upload the fixed package, I get a bugreport from you. Then I have
to update the changelog closing the bugreport and rebuild the package.
:)

> Sorry for the noise.
 No problem, next time I should wait more on you to file the bugreport.

Thanks for watching. Cheers,
Laszlo/GCS



Bug#817274: python-gevent: FTBFS: can't read debian/python-gevent-doc/...

2016-03-09 Thread Aaron M. Ucko
"László Böszörményi (GCS)"  writes:

>  Yes, seen that and upload is pending.

Great, thanks for the quick fix!

> While not a real issue, but is there any reason why you fire
> bugreports immediately?

Yes, my usual workflow is as follows:

- Run aptitude to update package lists.

- Run a personal script that reports binary packages that are new on
  amd64 and absent on i386, or vice versa.

- Check build.debian.org to rule out false positives (or in some cases
  identify buggy build dependencies).

- File reports.

- Reset aptitude's notion of which packages are new.

I prefer to follow this whole procedure fairly frequently so that I
don't have too many reports to file at any one time.

Sorry for the noise.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu



Bug#817274: python-gevent: FTBFS: can't read debian/python-gevent-doc/...

2016-03-09 Thread GCS
On Wed, Mar 9, 2016 at 5:49 PM, Aaron M. Ucko  wrote:
> Builds of python-gevent covering only its architecture-dependent
> binary packages (as on the autobuilders, or with dpkg-buildpackage -B)
> have been failing:
>
>   sed -i 's|http.*/btn_donateCC_LG.gif||' \
>   debian/python-gevent-doc/usr/share/doc/python-gevent-doc/html/sfc.html
>   sed: can't read 
> debian/python-gevent-doc/usr/share/doc/python-gevent-doc/html/sfc.html: No 
> such file or directory
[...]
> Please conditionalize this command appropriately.
 Yes, seen that and upload is pending.
While not a real issue, but is there any reason why you fire
bugreports immediately?

Cheers,
Laszlo/GCS



Bug#817274: python-gevent: FTBFS: can't read debian/python-gevent-doc/...

2016-03-09 Thread Aaron M. Ucko
Source: python-gevent
Version: 1.1.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of python-gevent covering only its architecture-dependent
binary packages (as on the autobuilders, or with dpkg-buildpackage -B)
have been failing:

  sed -i 's|http.*/btn_donateCC_LG.gif||' \
  debian/python-gevent-doc/usr/share/doc/python-gevent-doc/html/sfc.html
  sed: can't read 
debian/python-gevent-doc/usr/share/doc/python-gevent-doc/html/sfc.html: No such 
file or directory
  debian/rules:49: recipe for target 'override_dh_installdocs' failed
  make[1]: *** [override_dh_installdocs] Error 2
  make[1]: Leaving directory '/«PKGBUILDDIR»'
  debian/rules:10: recipe for target 'binary-arch' failed
  make: *** [binary-arch] Error 2

Please conditionalize this command appropriately.

Thanks!