Bug#1005016: libobject-pad-slotattr-final-perl: Object::Pad::SlotAttr::Final is replaced by Object::Pad::FieldAttr::Final

Damyan Ivanov dmn at debian.org
Mon May 23 11:37:23 BST 2022


-=| gregor herrmann, 09.02.2022 21:18:13 +0100 |=-
> > % apt-cache --names-only search libobject-pad-slot | grep -v 
> > dbgsym
> > libobject-pad-slotattr-final-perl - declare Object::Pad slots readonly after construction
> > libobject-pad-slotattr-isa-perl - apply class type constraints to Object::Pad slots
> > libobject-pad-slotattr-lazyinit-perl - lazily initialise Object::Pad slots at first read
> > libobject-pad-slotattr-trigger-perl - invoke an instance method after a :writer accessor
> 
> Alright, making this a bit more formal:
> - cloning the bug for the 3 other affected packages
> - marking them as serious as they currently block the perl 5.34
>   transition (by way of blocking the rebuilt arch:any libobject-pad-perl
>   as it breaks the 4 autopkgtests); this could be ignored, but the
>   4 packages are doomed anyway, so an RC bug makes removal from
>   testing more transparent.

I have just uploaded libobject-pad-fieldattr-final-perl to NEW. The 
others will follow.

I guess the deprecated packages should go the RM route? Perhaps after 
the new ones are accepted?

Not sure whether the waiting for the replacements to enter unstable is 
strictly necessary. To me it just feels polite to possible users

-- Damyan



More information about the pkg-perl-maintainers mailing list