[please CC] Hi,
On 19/06/11 16:30, Leo 'costela' Antunes wrote: > > I uploaded a new version of libevent to experimental which I'd like to > migrate to unstable as soon as possible. Since I'm the new guy helping > out with libevent and since this would be my first "bigish" transition, > I'd like to run it by the release team to make sure I'm not stepping on > anyone's toes. <snip> > Now I intended to write to -devel with all affected maintainers CC'd, > requesting further testing and input and after all have ack'd the > problems and have solutions in place, I'd go ahead with the upload to > unstable. > Does this sound like a reasonable plan? Did I miss something important? I didn't get an explicit answer about this, so I thought I might ask more directly: is it ok if I simply upload the new libevent to unstable? FYI, from all the starting FTBFSs, more than half have been dealt with or acknowledged by the respective maintainers: beanstalkd: fixed ladvd: fixed forked-daapd: version in experimental drops dependency python-event: (no answer to #632763) memcached: (no answer to #632764) lua-event: fixed honeyd: (no answer to #632765) Cheers -- Leo "costela" Antunes [insert a witty retort here] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org