On Fri, Dec 18, 2020 at 01:53:22PM +0900, Takatsugu Nokubi wrote:
> https://salsa.debian.org/debian/uim/-/merge_requests/9
>
> This is the fix request.
> Could you review the patch?
Thank you for your works. Reviewed and merged.
--
Regards,
dai
GPG Fingerprint = 0B29 D88E 42E6 B765 B8D
https://salsa.debian.org/debian/uim/-/merge_requests/9
This is the fix request.
Could you review the patch?
2020年12月14日(月) 18:24 :
> On Sun, Dec 13, 2020 at 02:35:58PM +0900, Takatsugu Nokubi wrote:
> > I made a simple patch to skip test-composer:
> >
> https://salsa.debian.org/debian/uim/-/com
On Sun, Dec 13, 2020 at 02:35:58PM +0900, Takatsugu Nokubi wrote:
> I made a simple patch to skip test-composer:
> https://salsa.debian.org/debian/uim/-/commit/3cd351b6f2b15fb3161e1d00ed4c8ba26925429b
> (Oh, I forgot to fix description of the patch)
Thank you for your work.
Please upload after des
I made a simple patch to skip test-composer:
https://salsa.debian.org/debian/uim/-/commit/3cd351b6f2b15fb3161e1d00ed4c8ba26925429b
(Oh, I forgot to fix description of the patch)
2020年12月13日(日) 10:36 :
> Control: forwarded -1 https://github.com/uim/uim/issues/167
>
> On Sat, Dec 12, 2020 at 02:50
Control: forwarded -1 https://github.com/uim/uim/issues/167
On Sat, Dec 12, 2020 at 02:50:52PM +0100, Sebastian Ramacher wrote:
> And it failed already twice for the Qt 5.15.2 transition, so I'm raising
> the severity. Please investigate and fix this issue.
Current upstream (not original authors
Control: severity -1 serious
On 2020-11-19 11:25:39 +0900, d...@debian.org wrote:
> Control: severity -1 important
>
> > Indeed, after the second retry uim built fine.
> >
> > Removing the block, but not closing because a race condition may be a
> > valid bug.
>
> I lower the severity once beca
Control: severity -1 important
> Indeed, after the second retry uim built fine.
>
> Removing the block, but not closing because a race condition may be a
> valid bug.
I lower the severity once because it is not always an build error.
--
Regards,
dai
GPG Fingerprint = 0B29 D88E 42E6 B76
> test2/test-suite.log is printed in build log:
I hadn't noticed that. Thank you.
I'll try to test more times, fortunately it is the upstream test
suite. So if I trying more times,
it should be reproduced.
Also I'll ask about it the upstream.
2020年11月18日(水) 9:53 :
>
> On Tue, Nov 17, 2020 at 09:
On Tue, Nov 17, 2020 at 09:11:54AM +0900, Takatsugu Nokubi wrote:
> I need the test2/test-suite.log file, so I had tried to reproduce it
> on abel twice, but
> I couldn't get the error, just succeeded.
>
> Can I get the test2/test-suite.log file from anywhere?
test2/test-suite.log is printed in b
On Sat, 31 Oct 2020 21:52:30 +0300 Dmitry Shachnev wrote:
> Control: unblock 972278 by -1
> > It built for me on abel, which is exactly the same hardware as the
> > buildds where it failed.
> >
> > This makes it feel more like a generic race condition that only happened
> > to hit here than an arm
Control: unblock 972278 by -1
On Sat, Oct 31, 2020 at 09:53:26AM +0200, Adrian Bunk wrote:
> On Fri, Oct 30, 2020 at 11:38:09PM +0100, Sebastian Ramacher wrote:
> >...
> > uim failed to build on armel:
> >...
>
> It built for me on abel, which is exactly the same hardware as the
> buildds where i
On Fri, Oct 30, 2020 at 11:38:09PM +0100, Sebastian Ramacher wrote:
>...
> uim failed to build on armel:
>...
It built for me on abel, which is exactly the same hardware as the
buildds where it failed.
This makes it feel more like a generic race condition that only happened
to hit here than an a
Source: uim
Version: 1:1.8.8-6.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
uim failed to build on armel:
| =
|uim 1.8.8: test2/test-suite.log
|
13 matches
Mail list logo
