Bug#925178: closed by Utkarsh Gupta (Bug#925178: fixed in ruby-globalid 0.4.2-1)

2019-05-11 Thread Paul Gevers
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 something like 0.4.2+really-...) with only the fix?

Ping. If not fixed in buster, this may lead to the removal of rails from
buster.

Paul

elbrus@respighi:~$ dak rm --no-action -R --suite=testing ruby-globalid
Will remove the following packages from testing:

ruby-globalid |0.3.6-2 | source, all

Maintainer: Debian Ruby Extras Maintainers


--- Reason ---

--

Checking reverse dependencies...
# Broken Depends:
rails: ruby-activejob

# Broken Build-Depends:
rails: ruby-globalid (>= 0.3.6)

Dependency problem found.



signature.asc
Description: OpenPGP digital signature


Bug#925178: closed by Utkarsh Gupta (Bug#925178: fixed in ruby-globalid 0.4.2-1)

2019-04-29 Thread Paul Gevers
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 are merged in upstream
>>* Bump debhelper compatibility level to 11
>>* Bump Standards-Version to 4.3.0 (no changes needed)
>>* Fix insecure URL
> 
> Thanks for the quick fix for this issue. However, due to the new
> upstream version and the debhelper compatibility bump this version is
> not eligible [1] for an unblock for buster.

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 something like 0.4.2+really-...) with only the fix?

Thanks
Paul



signature.asc
Description: OpenPGP digital signature


Bug#925178: closed by Utkarsh Gupta (Bug#925178: fixed in ruby-globalid 0.4.2-1)

2019-04-29 Thread Paul Gevers
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 the same ENOENT error:
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/ruby-globalid.html
> 
> Raising to serious, since this is also a FTBFS problem.

And changing the title to reflect the current problem.

Paul




signature.asc
Description: OpenPGP digital signature


Bug#925178: closed by Utkarsh Gupta (Bug#925178: fixed in ruby-globalid 0.4.2-1)

2019-04-20 Thread Santiago Vila
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 to fix regression (Closes: #925178)
> >* Drop patches that are merged in upstream
> >* Bump debhelper compatibility level to 11
> >* Bump Standards-Version to 4.3.0 (no changes needed)
> >* Fix insecure URL
> 
> Thanks for the quick fix for this issue. However, due to the new
> upstream version and the debhelper compatibility bump this version is
> not eligible [1] for an unblock for buster.
> 
> Did rails 2:5.2.2.1+dfsg-1 break ruby-globalid or did it only break the
> autopkgtest of it?

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 the same ENOENT error:

https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/ruby-globalid.html

Raising to serious, since this is also a FTBFS problem.

Thanks.



Bug#925178: closed by Utkarsh Gupta (Bug#925178: fixed in ruby-globalid 0.4.2-1)

2019-03-24 Thread Paul Gevers
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 compatibility level to 11
>* Bump Standards-Version to 4.3.0 (no changes needed)
>* Fix insecure URL

Thanks for the quick fix for this issue. However, due to the new
upstream version and the debhelper compatibility bump this version is
not eligible [1] for an unblock for buster.

Did rails 2:5.2.2.1+dfsg-1 break ruby-globalid or did it only break the
autopkgtest of it? I'm asking because this version of rails is fixing a
CVE's which we want in buster, but the autopkgtest failure (and the
freeze) is blocking it.

Paul

[1] https://release.debian.org/buster/freeze_policy.html



signature.asc
Description: OpenPGP digital signature