Hi,
On Mon, 29 Apr 2019 21:42:09 +0200 Paul Gevers wrote:
> As it turned out that the failure was *not* only a failure in the
> autopkgtest, but also in the build, we need a fix for buster. The above
> changes don't qualify, can you please revert the changes and upload the
> old version (version
Hi all,
On 24-03-2019 16:47, Paul Gevers wrote:
> On 24-03-2019 07:21, Debian Bug Tracking System wrote:
>> ruby-globalid (0.4.2-1) unstable; urgency=medium
>> .
>>* Team upload
>>* New upstream version 0.4.2
>>* Add patch to fix regression (Closes: #925178)
>>* Drop patches that
retitle 925178 ruby-globalid: FTBFS due to failing tests
thanks
On Sat, 20 Apr 2019 12:28:24 +0200 (CEST) Santiago Vila
wrote:
> In this case, breaking the tests is the same as breaking the package,
> because the tests are part of the package build and the package
> currently FTBFS in buster with
severity 925178 serious
tags 925178 + ftbfs
thanks
On Sun, 24 Mar 2019, Paul Gevers wrote:
> Hi all,
>
> On 24-03-2019 07:21, Debian Bug Tracking System wrote:
> > ruby-globalid (0.4.2-1) unstable; urgency=medium
> > .
> >* Team upload
> >* New upstream version 0.4.2
> >* Add patch
Hi all,
On 24-03-2019 07:21, Debian Bug Tracking System wrote:
> ruby-globalid (0.4.2-1) unstable; urgency=medium
> .
>* Team upload
>* New upstream version 0.4.2
>* Add patch to fix regression (Closes: #925178)
>* Drop patches that are merged in upstream
>* Bump debhelper co
5 matches
Mail list logo