[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#761816: marked as done (RM: libgdal-grass/1.10.1-2)

Your message dated Wed, 17 Sep 2014 09:27:07 +0200
with message-id <541937CB.1030105@debian.org>
and subject line Re: Bug#761816: RM: libgdal-grass/1.10.1-2
has caused the Debian Bug report #761816,
regarding RM: libgdal-grass/1.10.1-2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
761816: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761816
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: rm

The grass package was updated to 6.4.4-1 in unstable, which required an
update for libgdal-grass (1.10.1-3 available in unstable).

Currently both grass (6.4.4-1) and libgdal-grass (1.10.1-3) cannot
migrate to testing because updating grass in testing whould make
libgdal1-1.10.1-grass uninstallable. See: 

https://release.debian.org/migration/testing.pl?package=libgdal1-1.10.1-grass

By explicitly removing the libgdal1-1.10.1-grass revision that still
depends on GRASS 6.4.3 from testing, the updated revisions of grass and
libgdal-grass in unstable should be able to migrate to testing.

Kind Regards,

Bas

--- End Message ---
--- Begin Message --- 
On 16/09/14 12:03, Adam D. Barratt wrote:
> On 2014-09-16 10:18, Bas Couwenberg wrote:
>> The grass package was updated to 6.4.4-1 in unstable, which required an
>> update for libgdal-grass (1.10.1-3 available in unstable).
>>
>> Currently both grass (6.4.4-1) and libgdal-grass (1.10.1-3) cannot
>> migrate to testing because updating grass in testing whould make
>> libgdal1-1.10.1-grass uninstallable. See:
>>
>> https://release.debian.org/migration/testing.pl?package=libgdal1-1.10.1-grass
>>
>> By explicitly removing the libgdal1-1.10.1-grass revision that still
>> depends on GRASS 6.4.3 from testing, the updated revisions of grass and
>> libgdal-grass in unstable should be able to migrate to testing.
> 
> No, that's illogical. It doesn't make sense to remove a package from testing as
> an attempt to have a newer version of the same package migrate from unstable.
> Instead, one should work out how to make the migration of the new version succeed.
> 
> The underlying issue is that the two packages (grass and libgdal-grass) need to
> migrate to testing at the same time. The testing.pl script is a little stupid
> and only looks at the result of britney trying each source package separately.
> The migration of both packages at the same time is in fact being attempted, but
> failing. From the logs:
> 
> I: [Mon Sep 15 22:06:02 2014] - > Processing 'easy' hint from autohinter
> Trying easy from autohinter: grass/6.4.4-1 libgdal-grass/1.10.1-3
> leading: grass,libgdal-grass
> start: 12+25065: i-7:a-1:a-0:a-0:k-1:k-1:m-0:m-0:p-0:s-2:a-10122:p-14943
> orig: 12+25065: i-7:a-1:a-0:a-0:k-1:k-1:m-0:m-0:p-0:s-2:a-10122:p-14943
> easy: 13+25069: i-7:a-1:a-0:a-0:k-1:k-1:m-1:m-0:p-0:s-2:a-10122:p-14947
>     * mips: libgdal1-1.10.1-grass
>     * ppc64el: grass-core, grass-dev, grass-gui, libgdal1-1.10.1-grass
> 
> The ppc64el issue isn't a blocker, but mips is. The issue on mips is that
> libgdal1-1.10.1-grass was built against the old version of grass - libgdal-grass
> was uploaded 8 days ago but the new version of grass only built on mips 3 days ago.
> 
> I've scheduled a binNMU for libgdal-grass on mips which should resolve this.

And that worked. Closing.

Emilio

--- End Message ---
Reply to: