Now that libav transitioned to testing, and
https://release.debian.org/transitions/ says '100%' next to the libav
transition, what's left to be done here?
Best,
Reinhard
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On Tue, 2014-05-27 at 19:54 -0400, Reinhard Tartler wrote:
Now that libav transitioned to testing, and
https://release.debian.org/transitions/ says '100%' next to the libav
transition, what's left to be done here?
The old libraries need to be removed from testing.
britney's trying that, but
On Thu, May 8, 2014 at 20:35:55 -0400, Reinhard Tartler wrote:
On Tue, May 6, 2014 at 9:39 AM, Bálint Réczey bal...@balintreczey.hu wrote:
When do you plan starting the transition? How about opening it with
Libav 10.1? ;-)
I think we are in a pretty good position for startin now.
I
On Sun, May 11, 2014 at 9:16 AM, Julien Cristau jcris...@debian.org wrote:
On Thu, May 8, 2014 at 20:35:55 -0400, Reinhard Tartler wrote:
On Tue, May 6, 2014 at 9:39 AM, Bálint Réczey bal...@balintreczey.hu wrote:
When do you plan starting the transition? How about opening it with
Libav
On Sun, May 11, 2014 at 11:25:49 -0400, Reinhard Tartler wrote:
for the rest, I'd think that there is a very good chance that the
respective maintainers are going to fix them before they turn out to
be actual blockers of the transition. If they do, let's remove them
temporarily from testing.
On Sun, May 11, 2014 at 11:50 AM, Julien Cristau jcris...@debian.org wrote:
On Sun, May 11, 2014 at 11:25:49 -0400, Reinhard Tartler wrote:
for the rest, I'd think that there is a very good chance that the
respective maintainers are going to fix them before they turn out to
be actual blockers
Control: tag -1 confirmed
On Sun, May 11, 2014 at 12:05:55 -0400, Reinhard Tartler wrote:
On Sun, May 11, 2014 at 11:50 AM, Julien Cristau jcris...@debian.org wrote:
Would a timeline like this work for you:
- T: upload libav to unstable
- T+0: upgrade all FTBFS bugs to serious severity,
Processing control commands:
tag -1 confirmed
Bug #739079 [release.debian.org] transition: libav10
Added tag(s) confirmed.
--
739079: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739079
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to
On Sun, May 11, 2014 at 12:20 PM, Julien Cristau jcris...@debian.org wrote:
Control: tag -1 confirmed
On Sun, May 11, 2014 at 12:05:55 -0400, Reinhard Tartler wrote:
On Sun, May 11, 2014 at 11:50 AM, Julien Cristau jcris...@debian.org wrote:
Would a timeline like this work for you:
- T:
On dom, mag 11, 2014 at 12:05:55 -0400, Reinhard Tartler wrote:
On Sun, May 11, 2014 at 11:50 AM, Julien Cristau jcris...@debian.org wrote:
For reference last time took 2 months.
I'll be doing my best to make it happen faster this time.
If help is needed I can lend a hand.
Cheers
On Tue, May 6, 2014 at 9:39 AM, Bálint Réczey bal...@balintreczey.hu wrote:
When do you plan starting the transition? How about opening it with
Libav 10.1? ;-)
I think we are in a pretty good position for startin now.
I agree. Let me upload 10.1 this weekend to unstable to finally start
this
Hi Reinhard,
2014-03-01 17:01 GMT+01:00 Reinhard Tartler siret...@gmail.com:
On Tue, Feb 18, 2014 at 4:48 PM, Moritz Mühlenhoff j...@inutil.org wrote:
I made a rebuild and the transitions isn't ready to go at all.
IMO the API changes are far too agressive; if 2/3 of all packages in
the
I uploaded a new version of bino to mentors.d.n which fixes the compilation
with libav10 by backporting some upstream commits, but I would need a sponsor
to upload it for me, as my usual sponsor will be on vacation the next couple
of weeks,
https://mentors.debian.net/package/bino
On Tue, Feb 18, 2014 at 4:48 PM, Moritz Mühlenhoff j...@inutil.org wrote:
I made a rebuild and the transitions isn't ready to go at all.
IMO the API changes are far too agressive; if 2/3 of all packages in
the archive FTBFS, the affected APIs are clearly not that deprecated.
I can understand
Hi,
(a libav developer responsible for most of the breaks here)
I do not think bringing back the CODEC_ID_* stuff is such a great idea.
The reasons are:
- keeping compatibility in this case requires a rather ugly hack (because in c++
different enums are not compatible), which has to my
(Putting the bug back into the loop.)
On 2014-02-16 21:47:25, Moritz Mühlenhoff wrote:
On Sun, Feb 16, 2014 at 03:44:01PM -0500, Reinhard Tartler wrote:
On Sun, Feb 16, 2014 at 11:22 AM, Moritz Mühlenhoff j...@inutil.org wrote:
Reinhard Tartler siret...@tauware.de schrieb:
Package:
On Tue, Feb 18, 2014 at 08:16:05PM +0100, Sebastian Ramacher wrote:
(Putting the bug back into the loop.)
On 2014-02-16 21:47:25, Moritz Mühlenhoff wrote:
On Sun, Feb 16, 2014 at 03:44:01PM -0500, Reinhard Tartler wrote:
On Sun, Feb 16, 2014 at 11:22 AM, Moritz Mühlenhoff j...@inutil.org
On Sat, Feb 15, 2014 at 08:57:47PM +0100, Julien Cristau wrote:
On Sat, Feb 15, 2014 at 19:37:54 +0100, Sebastian Ramacher wrote:
Hi Reinhard
On 2014-02-15 17:42:41, Reinhard Tartler wrote:
Unfortunately, this new release does break a number of packages in the
debian archive. At
Reinhard Tartler siret...@tauware.de schrieb:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hi,
We have a new libav transition pending. Libav 10 is prepared in
debian/experimental, and I've started to build packges against
On Sun, Feb 16, 2014 at 11:22 AM, Moritz Mühlenhoff j...@inutil.org wrote:
Reinhard Tartler siret...@tauware.de schrieb:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hi,
We have a new libav transition pending. Libav 10 is
On Sun, Feb 16, 2014 at 03:44:01PM -0500, Reinhard Tartler wrote:
On Sun, Feb 16, 2014 at 11:22 AM, Moritz Mühlenhoff j...@inutil.org wrote:
Reinhard Tartler siret...@tauware.de schrieb:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hi,
We have a new libav transition pending. Libav 10 is prepared in
debian/experimental, and I've started to build packges against this new
version; in fact, more or more packages
Hi Reinhard
On 2014-02-15 17:42:41, Reinhard Tartler wrote:
Unfortunately, this new release does break a number of packages in the
debian archive. At upstream, we are concerned about this and have
conducted a survey about the fallout here:
https://etherpad.mozilla.org/mnrZI5XlxP
I'm not a
On Sat, Feb 15, 2014 at 19:37:54 +0100, Sebastian Ramacher wrote:
Hi Reinhard
On 2014-02-15 17:42:41, Reinhard Tartler wrote:
Unfortunately, this new release does break a number of packages in the
debian archive. At upstream, we are concerned about this and have
conducted a survey about
24 matches
Mail list logo
