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

Bug#796345: Status report on perl 5.22 transition readiness (30th Sept)



On Thu, Dec 31, 2015 at 19:11:03 +0100, Julien Cristau wrote:

> On Thu, Dec 31, 2015 at 02:55:53 +0100, Emilio Pozuelo Monfort wrote:
> 
> > Last britney run had this:
> > 
> >     * amd64: ganglia-nagios-bridge, gendarme, icinga, icinga-core, icinga-dbg,
> > kde-full, kdepim, kleopatra, libccs-perl,
> > libicsharpcode-nrefactory-cecil5.0-cil, libicsharpcode-nrefactory-cil-dev,
> > libicsharpcode-nrefactory-csharp5.0-cil, libicsharpcode-nrefactory-ikvm5.0-cil,
> > libicsharpcode-nrefactory-xml5.0-cil, libicsharpcode-nrefactory5.0-cil,
> > libmono-debugger-libs-cil-dev, libmono-debugger-soft-cil, libmono-debugging-cil,
> > libmono-debugging-soft-cil, libperl5.20, libvtkgdcm-java, libvtkgdcm2.4,
> > mono-tools-devel, mono-tools-gui, nrefactory-samples, perl-modules, sdb,
> > syslog-nagios-bridge, wnn7egg
> [...]
> > 
> > powerpc needs some cleanup for the mono bits, it seems. e.g. libgdk3.0-cil-dev
> > should have been removed on that architecture but is still present there.
> > 
> > icinga needs ageing.
> > 
> > There are some arch:all packages that break (see amd64/i386). Maybe some can be
> > removed or need ageing.
> > 
> > Unfortunately I have run out of time and can't look at this anymore. If someone
> > can take it up and try to get things fixed, and eventually force it (to ignore
> > cruft / libccs-perl), that'd be great. Otherwise I can keep looking at it when I
> > get back.
> > 
> Looking now... There's a number of badly timed uploads getting in the
> way, at least courier, inn2, icinga and gnumeric.  I'll see where this
> all gets me.
> 
On the mono side I end up with
remove nrefactory/5.3.0+20130718.73b6d0f-2 mono-debugger-libs/0+20131201.3459502-1 sdb/1.2-1

3 packages from the mono-tools source break due to a dep on
libmono-cecil-private-cil (<< 3.2.9): gendarme, mono-tools-devel,
mono-tools-gui.  AFAICT that needs a sourceful upload of mono-tools.

I might go ahead and force this in anyway, and fix up the leftover
pieces afterwards.

Cheers,
Julien

Attachment: signature.asc
Description: PGP signature


Reply to: