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 publi
"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 rep
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 t
"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
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
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
6 matches
Mail list logo
