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

Bug#654237: marked as done (transition: libav 0.8)



Your message dated Thu, 05 Jan 2012 11:57:07 +0100
with message-id <87k456a03g.fsf@faui43f.informatik.uni-erlangen.de>
and subject line Re: Bug#654237: Processed: relevant bugs for libav transition
has caused the Debian Bug report #654237,
regarding transition: libav 0.8
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.)


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

Hi,

I'd like to schedule a transition from libav 0.7 -> libav 0.8. As this
release is ABI-compatible to 0.7, only the shlibs file has been
bumped. However, due to cleaned up header dependencies, a number of
packages in wheezy start to FTBFS.

I took http://release.debian.org/transitions/html/libav.html as basis
for the lists of packages in wheezy to rebuild. Out of 69 packages, 14
packages FTBFS because of this. These build failures have been reported
and user tagged here:

http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=siretart@tauware.de;tag=ftbfs-libav0.8

AFAIUI http://release.debian.org/transitions/, this might (or might
not?) interfere with the vtk5.8 and opencv transition.

Please tell me when its a convinent time to start this transition.

Cheers,
Reinhard

-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4



--- End Message ---
--- Begin Message ---
On Di, Jan 03, 2012 at 17:05:34 (CET), Jonathan Nieder wrote:

> unblock 654237 by 654230 641508 651625 652763 652061
> quit
>
> Hi Reinhard,
>
> Reinhard Tartler wrote:
>
>> Are these bugs really blocking the upload of libav 0.8?
>
> I am not the release team, but probably no.  Once there are only a few
> left, the release team might signal that it is a convenient enough
> time to upload and they can be fixed afterward.  And some packages can
> be temporarily removed from testing to avoid slowing a transition down
> too much.
>
> Plus I was too lazy of a reader to notice that libav 0.8 is
> ABI-compatible with libav 0.7, making this way easier than a typical
> transition (so the random RC bugs are not actually relevant; only the
> ftbfs bugs might be).  Actually I am not sure why this is called a
> transition at all.

You're right, I wasn't thinking straight. It surely would be to much
work if each shlibs bump would have to be coordinated with the release
team. I'm therefore closing this bug with this email and am going to
upload to unstable with the next upstream beta release. This will
probably happen this weekend or next week.

Cheers,
Reinhard.

-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4


--- End Message ---

Reply to: