Re: cnvkit update to 0.9.6 needs Fwd: python-pomegranate_0.11.1-1_amd64.changes is NEW
python-pomegranate was accepted on 2019-08-31, but now we need a source only upload
Steffen, can you do a source only upload of python-pomegranate so cnvkit can migrate?
On Tue, Sep 03, 2019 at 10:41:14AM +0200, Steffen Möller wrote:
> > > I have asked our ftpmasters to consider fast-tracking the pomegranate
> > > module. We'll see.
> > Good.
> And I should now take this opportunity to thank our ftpmasters who have
> just accepted pomegranate. cnvkit I then also updated almost instantly.
Yep. Ftpmasters are usually happy if you provide some help in ranking
> > > Sidenote: I herewith confirm that Andreas' "routine-update" script is
> > > well worth a look. In my experience this also changes how I look at
> > > patches - you avoid them, invest extra time into sending them upstream.
> > :-)
> The downside of course is that one "quickly" helps out with some team
> routine updates which then turn out to be less of a routine.
I'm absolutely aware of this since I have probably had my fingers in
about 99% of our packages. But before routine-update the "surprise"
about not so routine-tasks was the same. Just the real routine is
simplified. Also autopkgtests are reducing the routine-fun. The
example of mapdamage (see my other mail) shows: If you really look at
the tests than something might stop you from uploading. But its good
for the final user experience.
> Like that
> cnvkit one. So, one's time invested into Debian may remain invariant,
> but one's yield for the distro may increase.
Considering that someone needs to do the work it helps if at least
the routine tasks are simple.
> We should not forget that we still have a new queue problem. pomegranate
> has overtaken about 5 packages of mine in new and these have another
> 5-10 reverse dependencies that I have not yet uploaded to new that all
> aim at the RNAseq workflows.
You can try to send another ranking to ftpmaster.