libpng 1.6 upgrade and subslotting (and misuse of subslotting when there is also normal slotting)

classic Classic list List threaded Threaded
19 messages Options
Reply | Threaded
Open this post in threaded view
|

libpng 1.6 upgrade and subslotting (and misuse of subslotting when there is also normal slotting)

Samuli Suominen-4
libpng 1.6 is in portage, but temporarily without KEYWORDS, pending on
testign and this conversion, help would be much appericiated with
converting the tree to use automatic rebuilds for the upgrade

Because there is binary-only SLOT="1.2" of libpng, none of these are
correct:

$ grep -r 'media-libs/libpng.*:=' */*/*.ebuild
app-misc/tracker/tracker-0.14.4.ebuild: >=media-libs/libpng-1.2:=
app-misc/tracker/tracker-0.14.5.ebuild: >=media-libs/libpng-1.2:=
app-misc/tracker/tracker-0.16.0.ebuild: >=media-libs/libpng-1.2:=
app-misc/tracker/tracker-9999.ebuild: >=media-libs/libpng-1.2:=
media-gfx/digikam/digikam-3.0.0.ebuild: media-libs/libpng:=
media-gfx/digikam/digikam-3.1.0.ebuild: media-libs/libpng:=
media-plugins/gst-plugins-gl/gst-plugins-gl-0.10.3.ebuild:
 >=media-libs/libpng-1.4:=
media-plugins/gst-plugins-libpng/gst-plugins-libpng-1.0.5.ebuild:RDEPEND=">=media-libs/libpng-1.4:="
media-plugins/gst-plugins-libpng/gst-plugins-libpng-1.0.6.ebuild:RDEPEND=">=media-libs/libpng-1.4:="
www-client/chromium/chromium-27.0.1453.12.ebuild: media-libs/libpng:=
www-client/chromium/chromium-27.0.1453.3.ebuild: media-libs/libpng:=
www-client/chromium/chromium-9999-r1.ebuild: media-libs/libpng:=

They should all be :0= to avoid matching the :1.2 SLOT.

Plus some hundreds are completely without subslotting:

$ grep -r 'media-libs/libpng' */*/*.ebuild |grep -v ':.*='
output -> http://bpaste.net/show/89268/

Thanks,
Samuli

Reply | Threaded
Open this post in threaded view
|

Re: libpng 1.6 upgrade and subslotting (and misuse of subslotting when there is also normal slotting)

Pacho Ramos
El vie, 05-04-2013 a las 23:44 +0300, Samuli Suominen escribió:
[...]
> Plus some hundreds are completely without subslotting:
>
> $ grep -r 'media-libs/libpng' */*/*.ebuild |grep -v ':.*='
> output -> http://bpaste.net/show/89268/
>
> Thanks,
> Samuli
>
>

Do all packages really require rebuilding? (for start adding := for
libpng deps)


Reply | Threaded
Open this post in threaded view
|

Re: libpng 1.6 upgrade and subslotting (and misuse of subslotting when there is also normal slotting)

Ian Stakenvicius-2


On 2013-04-05, at 5:17 PM, Pacho Ramos <[hidden email]> wrote:

> El vie, 05-04-2013 a las 23:44 +0300, Samuli Suominen escribió:
> [...]
>> Plus some hundreds are completely without subslotting:
>>
>> $ grep -r 'media-libs/libpng' */*/*.ebuild |grep -v ':.*='
>> output -> http://bpaste.net/show/89268/
>>
>> Thanks,
>> Samuli
>
> Do all packages really require rebuilding? (for start adding := for
> libpng deps)
>
>

Nearly all -- libpng15.so will disappear and libpng16.so will replace it.  
Reply | Threaded
Open this post in threaded view
|

Re: libpng 1.6 upgrade and subslotting (and misuse of subslotting when there is also normal slotting)

Michael Mol
In reply to this post by Samuli Suominen-4
On 04/05/2013 04:44 PM, Samuli Suominen wrote:

> libpng 1.6 is in portage, but temporarily without KEYWORDS, pending on
> testign and this conversion, help would be much appericiated with
> converting the tree to use automatic rebuilds for the upgrade
>
> Because there is binary-only SLOT="1.2" of libpng, none of these are
> correct:
>
> $ grep -r 'media-libs/libpng.*:=' */*/*.ebuild
> app-misc/tracker/tracker-0.14.4.ebuild:    >=media-libs/libpng-1.2:=
> app-misc/tracker/tracker-0.14.5.ebuild:    >=media-libs/libpng-1.2:=
> app-misc/tracker/tracker-0.16.0.ebuild:    >=media-libs/libpng-1.2:=
> app-misc/tracker/tracker-9999.ebuild:    >=media-libs/libpng-1.2:=
> media-gfx/digikam/digikam-3.0.0.ebuild:    media-libs/libpng:=
> media-gfx/digikam/digikam-3.1.0.ebuild:    media-libs/libpng:=
> media-plugins/gst-plugins-gl/gst-plugins-gl-0.10.3.ebuild:
>>=media-libs/libpng-1.4:=
> media-plugins/gst-plugins-libpng/gst-plugins-libpng-1.0.5.ebuild:RDEPEND=">=media-libs/libpng-1.4:="
>
> media-plugins/gst-plugins-libpng/gst-plugins-libpng-1.0.6.ebuild:RDEPEND=">=media-libs/libpng-1.4:="
>
> www-client/chromium/chromium-27.0.1453.12.ebuild:    media-libs/libpng:=
> www-client/chromium/chromium-27.0.1453.3.ebuild:    media-libs/libpng:=
> www-client/chromium/chromium-9999-r1.ebuild:    media-libs/libpng:=
>
> They should all be :0= to avoid matching the :1.2 SLOT.
>
> Plus some hundreds are completely without subslotting:
>
> $ grep -r 'media-libs/libpng' */*/*.ebuild |grep -v ':.*='
> output -> http://bpaste.net/show/89268/
>
> Thanks,
> Samuli
>
I'd love to help, but I haven't done much at all with ebuild munging. If
there's a list of basic translation instructions that would work for
most ebuilds, I could certainly knock off a few.


signature.asc (567 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: libpng 1.6 upgrade and subslotting (and misuse of subslotting when there is also normal slotting)

Samuli Suominen-4
In reply to this post by Pacho Ramos
On 06/04/13 00:17, Pacho Ramos wrote:

> El vie, 05-04-2013 a las 23:44 +0300, Samuli Suominen escribió:
> [...]
>> Plus some hundreds are completely without subslotting:
>>
>> $ grep -r 'media-libs/libpng' */*/*.ebuild |grep -v ':.*='
>> output -> http://bpaste.net/show/89268/
>>
>> Thanks,
>> Samuli
>>
>>
>
> Do all packages really require rebuilding? (for start adding := for
> libpng deps)
>
>

yep, everything, because libpng doesn't come with any tools, all of the
uses are for the library (and the headers)



Reply | Threaded
Open this post in threaded view
|

Re: libpng 1.6 upgrade and subslotting (and misuse of subslotting when there is also normal slotting)

Samuli Suominen-4
In reply to this post by Pacho Ramos
On 06/04/13 00:17, Pacho Ramos wrote:

> El vie, 05-04-2013 a las 23:44 +0300, Samuli Suominen escribió:
> [...]
>> Plus some hundreds are completely without subslotting:
>>
>> $ grep -r 'media-libs/libpng' */*/*.ebuild |grep -v ':.*='
>> output -> http://bpaste.net/show/89268/
>>
>> Thanks,
>> Samuli
>>
>>
>
> Do all packages really require rebuilding? (for start adding := for
> libpng deps)

you mean :0= of course :)

Reply | Threaded
Open this post in threaded view
|

Re: libpng 1.6 upgrade and subslotting (and misuse of subslotting when there is also normal slotting)

Mike Gilbert-2
In reply to this post by Samuli Suominen-4
On Fri, Apr 5, 2013 at 4:44 PM, Samuli Suominen <[hidden email]> wrote:

> libpng 1.6 is in portage, but temporarily without KEYWORDS, pending on
> testign and this conversion, help would be much appericiated with converting
> the tree to use automatic rebuilds for the upgrade
>
> Because there is binary-only SLOT="1.2" of libpng, none of these are
> correct:
> ...
> www-client/chromium/chromium-27.0.1453.12.ebuild:       media-libs/libpng:=
> www-client/chromium/chromium-27.0.1453.3.ebuild:        media-libs/libpng:=
> www-client/chromium/chromium-9999-r1.ebuild:    media-libs/libpng:=
>
> They should all be :0= to avoid matching the :1.2 SLOT.
>

chromium is fixed, thanks.

> Plus some hundreds are completely without subslotting:
>

Minor correction: hundreds of packages lack "slot-operator"
dependencies. Slot-operators and subslots are related, but are not the
same thing.

Reply | Threaded
Open this post in threaded view
|

Re: libpng 1.6 upgrade and subslotting (and misuse of subslotting when there is also normal slotting)

Ben de Groot-2
In reply to this post by Samuli Suominen-4

On 6 Apr, 2013 4:46 AM, "Samuli Suominen" <[hidden email]> wrote:
>
> libpng 1.6 is in portage, but temporarily without KEYWORDS, pending on testign and this conversion, help would be much appericiated with converting the tree to use automatic rebuilds for the upgrade
>
> Because there is binary-only SLOT="1.2" of libpng, none of these are correct:
>
> $ grep -r 'media-libs/libpng.*:=' */*/*.ebuild
> app-misc/tracker/tracker-0.14.4.ebuild: >=media-libs/libpng-1.2:=
> app-misc/tracker/tracker-0.14.5.ebuild: >=media-libs/libpng-1.2:=
> app-misc/tracker/tracker-0.16.0.ebuild: >=media-libs/libpng-1.2:=
> app-misc/tracker/tracker-9999.ebuild:   >=media-libs/libpng-1.2:=
> media-gfx/digikam/digikam-3.0.0.ebuild: media-libs/libpng:=
> media-gfx/digikam/digikam-3.1.0.ebuild: media-libs/libpng:=
> media-plugins/gst-plugins-gl/gst-plugins-gl-0.10.3.ebuild: >=media-libs/libpng-1.4:=
> media-plugins/gst-plugins-libpng/gst-plugins-libpng-1.0.5.ebuild:RDEPEND=">=media-libs/libpng-1.4:="
> media-plugins/gst-plugins-libpng/gst-plugins-libpng-1.0.6.ebuild:RDEPEND=">=media-libs/libpng-1.4:="
> www-client/chromium/chromium-27.0.1453.12.ebuild:       media-libs/libpng:=
> www-client/chromium/chromium-27.0.1453.3.ebuild:        media-libs/libpng:=
> www-client/chromium/chromium-9999-r1.ebuild:    media-libs/libpng:=
>
> They should all be :0= to avoid matching the :1.2 SLOT.
>
> Plus some hundreds are completely without subslotting:
>
> $ grep -r 'media-libs/libpng' */*/*.ebuild |grep -v ':.*='
> output -> http://bpaste.net/show/89268/
>
> Thanks,
> Samuli
>

This would be a good opportunity to use the latest eapi in all those packages. Would adding the :0= slot operator, and upping the eapi, warrant a revbump tho, or can we simply do it “in place"?

Reply | Threaded
Open this post in threaded view
|

Re: libpng 1.6 upgrade and subslotting (and misuse of subslotting when there is also normal slotting)

Ian Stakenvicius-2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 05/04/13 09:52 PM, Ben de Groot wrote:

> On 6 Apr, 2013 4:46 AM, "Samuli Suominen" <[hidden email]
> <mailto:[hidden email]>> wrote:
>>
>> libpng 1.6 is in portage, but temporarily without KEYWORDS,
>> pending on
> testign and this conversion, help would be much appericiated with
> converting the tree to use automatic rebuilds for the upgrade
>>
>> Because there is binary-only SLOT="1.2" of libpng, none of these
>> are
> correct:
>>
>> $ grep -r 'media-libs/libpng.*:=' */*/*.ebuild
>> app-misc/tracker/tracker-0.14.4.ebuild:
>> >=media-libs/libpng-1.2:= app-misc/tracker/tracker-0.14.5.ebuild:
>> >=media-libs/libpng-1.2:= app-misc/tracker/tracker-0.16.0.ebuild:
>> >=media-libs/libpng-1.2:= app-misc/tracker/tracker-9999.ebuild:
>> >=media-libs/libpng-1.2:= media-gfx/digikam/digikam-3.0.0.ebuild:
>> media-libs/libpng:= media-gfx/digikam/digikam-3.1.0.ebuild:
>> media-libs/libpng:=
>> media-plugins/gst-plugins-gl/gst-plugins-gl-0.10.3.ebuild:
>> =media-libs/libpng-1.4:=
>>
> media-plugins/gst-plugins-libpng/gst-plugins-libpng-1.0.5.ebuild:RDEPEND=">=media-libs/libpng-1.4:="
>>
>
>
media-plugins/gst-plugins-libpng/gst-plugins-libpng-1.0.6.ebuild:RDEPEND=">=media-libs/libpng-1.4:="

>> www-client/chromium/chromium-27.0.1453.12.ebuild:
> media-libs/libpng:=
>> www-client/chromium/chromium-27.0.1453.3.ebuild:
> media-libs/libpng:=
>> www-client/chromium/chromium-9999-r1.ebuild:
>> media-libs/libpng:=
>>
>> They should all be :0= to avoid matching the :1.2 SLOT.
>>
>> Plus some hundreds are completely without subslotting:
>>
>> $ grep -r 'media-libs/libpng' */*/*.ebuild |grep -v ':.*=' output
>> -> http://bpaste.net/show/89268/
>>
>> Thanks, Samuli
>>
>
> This would be a good opportunity to use the latest eapi in all
> those packages. Would adding the :0= slot operator, and upping the
> eapi, warrant a revbump tho, or can we simply do it “in place"?
>

Revbump -- very important in this case, as the slot-operator dep
(iirc) does not take effect to allow sub-slot-triggered until after a
version with the slot-operator has been emerged.

So we want users to re-emerge packages either at the same time
libpng-1.6 hits the tree, or beforehand so that they will be triggered
for rebuild when libpng-1.6 hits.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iF4EAREIAAYFAlFfhe4ACgkQ2ugaI38ACPC3/QD/UZp5DZTNjVcrEgbIWHjqS4W7
yQIYDQtqQnenC04hodsA/0AIvZH0+fvUtuqyxGX8tvBmHyPOLNjda2iL3Mtp98Sy
=O7qD
-----END PGP SIGNATURE-----

Reply | Threaded
Open this post in threaded view
|

Re: libpng 1.6 upgrade and subslotting (and misuse of subslotting when there is also normal slotting)

Alexandre Rostovtsev-2
In reply to this post by Samuli Suominen-4
On Fri, 2013-04-05 at 23:44 +0300, Samuli Suominen wrote:

> libpng 1.6 is in portage, but temporarily without KEYWORDS, pending on
> testign and this conversion, help would be much appericiated with
> converting the tree to use automatic rebuilds for the upgrade
>
> Because there is binary-only SLOT="1.2" of libpng, none of these are
> correct:
>
> $ grep -r 'media-libs/libpng.*:=' */*/*.ebuild
> app-misc/tracker/tracker-0.14.4.ebuild: >=media-libs/libpng-1.2:=
> app-misc/tracker/tracker-0.14.5.ebuild: >=media-libs/libpng-1.2:=
> app-misc/tracker/tracker-0.16.0.ebuild: >=media-libs/libpng-1.2:=
> app-misc/tracker/tracker-9999.ebuild: >=media-libs/libpng-1.2:=
> media-gfx/digikam/digikam-3.0.0.ebuild: media-libs/libpng:=
> media-gfx/digikam/digikam-3.1.0.ebuild: media-libs/libpng:=
> media-plugins/gst-plugins-gl/gst-plugins-gl-0.10.3.ebuild:
>  >=media-libs/libpng-1.4:=
> media-plugins/gst-plugins-libpng/gst-plugins-libpng-1.0.5.ebuild:RDEPEND=">=media-libs/libpng-1.4:="
> media-plugins/gst-plugins-libpng/gst-plugins-libpng-1.0.6.ebuild:RDEPEND=">=media-libs/libpng-1.4:="
> www-client/chromium/chromium-27.0.1453.12.ebuild: media-libs/libpng:=
> www-client/chromium/chromium-27.0.1453.3.ebuild: media-libs/libpng:=
> www-client/chromium/chromium-9999-r1.ebuild: media-libs/libpng:=
>
> They should all be :0= to avoid matching the :1.2 SLOT.

Thanks for checking this; tracker and gst-plugins-{gl,libpng} ebuilds
are now fixed.


Reply | Threaded
Open this post in threaded view
|

Re: libpng 1.6 upgrade and subslotting (and misuse of subslotting when there is also normal slotting)

Alexis Ballier-2
In reply to this post by Ian Stakenvicius-2
On Fri, 05 Apr 2013 22:18:22 -0400
Ian Stakenvicius <[hidden email]> wrote:

>
> Revbump -- very important in this case, as the slot-operator dep
> (iirc) does not take effect to allow sub-slot-triggered until after a
> version with the slot-operator has been emerged.
>
> So we want users to re-emerge packages either at the same time
> libpng-1.6 hits the tree, or beforehand so that they will be triggered
> for rebuild when libpng-1.6 hits.
>


so we force two rebuilds instead of one ?

Reply | Threaded
Open this post in threaded view
|

Re: libpng 1.6 upgrade and subslotting (and misuse of subslotting when there is also normal slotting)

Mike Gilbert-2
On Sat, Apr 6, 2013 at 10:33 AM, Alexis Ballier <[hidden email]> wrote:

> On Fri, 05 Apr 2013 22:18:22 -0400
> Ian Stakenvicius <[hidden email]> wrote:
>
>>
>> Revbump -- very important in this case, as the slot-operator dep
>> (iirc) does not take effect to allow sub-slot-triggered until after a
>> version with the slot-operator has been emerged.
>>
>> So we want users to re-emerge packages either at the same time
>> libpng-1.6 hits the tree, or beforehand so that they will be triggered
>> for rebuild when libpng-1.6 hits.
>>
>
>
> so we force two rebuilds instead of one ?
>

Well, ideally you would do it in conjunction with a version bump
rather than a revbump.

But failing that, a revbump for an EAPI + dependency change seems like
the safest option.

Reply | Threaded
Open this post in threaded view
|

Re: libpng 1.6 upgrade and subslotting (and misuse of subslotting when there is also normal slotting)

Alexis Ballier-2
On Sat, 6 Apr 2013 11:02:14 -0400
Mike Gilbert <[hidden email]> wrote:

> On Sat, Apr 6, 2013 at 10:33 AM, Alexis Ballier <[hidden email]>
> wrote:
> > On Fri, 05 Apr 2013 22:18:22 -0400
> > Ian Stakenvicius <[hidden email]> wrote:
> >
> >>
> >> Revbump -- very important in this case, as the slot-operator dep
> >> (iirc) does not take effect to allow sub-slot-triggered until
> >> after a version with the slot-operator has been emerged.
> >>
> >> So we want users to re-emerge packages either at the same time
> >> libpng-1.6 hits the tree, or beforehand so that they will be
> >> triggered for rebuild when libpng-1.6 hits.
> >>
> >
> >
> > so we force two rebuilds instead of one ?
> >
>
> Well, ideally you would do it in conjunction with a version bump
> rather than a revbump.
>
> But failing that, a revbump for an EAPI + dependency change seems like
> the safest option.
>

or: we can do the conversion in place, tell people to
@preserve-rebuild / revdep-rebuild and get the benefits next time :)

Reply | Threaded
Open this post in threaded view
|

Re: libpng 1.6 upgrade and subslotting (and misuse of subslotting when there is also normal slotting)

Mike Gilbert-2
On Sat, Apr 6, 2013 at 11:09 AM, Alexis Ballier <[hidden email]> wrote:

> On Sat, 6 Apr 2013 11:02:14 -0400
> Mike Gilbert <[hidden email]> wrote:
>
>> On Sat, Apr 6, 2013 at 10:33 AM, Alexis Ballier <[hidden email]>
>> wrote:
>> > On Fri, 05 Apr 2013 22:18:22 -0400
>> > Ian Stakenvicius <[hidden email]> wrote:
>> >
>> >>
>> >> Revbump -- very important in this case, as the slot-operator dep
>> >> (iirc) does not take effect to allow sub-slot-triggered until
>> >> after a version with the slot-operator has been emerged.
>> >>
>> >> So we want users to re-emerge packages either at the same time
>> >> libpng-1.6 hits the tree, or beforehand so that they will be
>> >> triggered for rebuild when libpng-1.6 hits.
>> >>
>> >
>> >
>> > so we force two rebuilds instead of one ?
>> >
>>
>> Well, ideally you would do it in conjunction with a version bump
>> rather than a revbump.
>>
>> But failing that, a revbump for an EAPI + dependency change seems like
>> the safest option.
>>
>
> or: we can do the conversion in place, tell people to
> @preserve-rebuild / revdep-rebuild and get the benefits next time :)
>

I'm just not sure how the package managers like an in-place EAPI
change. If it works, great.

Reply | Threaded
Open this post in threaded view
|

Re: libpng 1.6 upgrade and subslotting (and misuse of subslotting when there is also normal slotting)

Ciaran McCreesh-4
On Sat, 6 Apr 2013 11:13:36 -0400
Mike Gilbert <[hidden email]> wrote:
> I'm just not sure how the package managers like an in-place EAPI
> change. If it works, great.

If you don't revbump when going from an EAPI that doesn't have subslots
to one that does, and then people start using subslot deps upon that
package, it gets pretty icky. So I would highly encourage always
revbumping at least when going to EAPI 5.

--
Ciaran McCreesh

signature.asc (205 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: libpng 1.6 upgrade and subslotting (and misuse of subslotting when there is also normal slotting)

Alexis Ballier-2
On Sat, 6 Apr 2013 16:27:33 +0100
Ciaran McCreesh <[hidden email]> wrote:

> On Sat, 6 Apr 2013 11:13:36 -0400
> Mike Gilbert <[hidden email]> wrote:
> > I'm just not sure how the package managers like an in-place EAPI
> > change. If it works, great.
>
> If you don't revbump when going from an EAPI that doesn't have
> subslots to one that does, and then people start using subslot deps
> upon that package, it gets pretty icky. So I would highly encourage
> always revbumping at least when going to EAPI 5.
>

we are talking about the other way around I think: package with the
subslot is already eapi 5, package wanting the := dep is converted in
place

in that case, installed package will not have the := dep in vdb, thus
will not be rebuilt; when updating libpng, old school methods will still
work, and once that is done the := dep will do its job in the future.

I agree it'd be nice to have everything rebuilt automatically when
going from libpng 1.5 to 1.6 but I'm seeing it the other way: I don't
understand why I need to rebuild half of my system just to be able to
automatically rebuild it again later.


Alexis.

Reply | Threaded
Open this post in threaded view
|

Re: libpng 1.6 upgrade and subslotting (and misuse of subslotting when there is also normal slotting)

Ian Stakenvicius-2
In reply to this post by Alexis Ballier-2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 06/04/13 10:33 AM, Alexis Ballier wrote:

> On Fri, 05 Apr 2013 22:18:22 -0400 Ian Stakenvicius
> <[hidden email]> wrote:
>
>>
>> Revbump -- very important in this case, as the slot-operator dep
>> (iirc) does not take effect to allow sub-slot-triggered until
>> after a version with the slot-operator has been emerged.
>>
>> So we want users to re-emerge packages either at the same time
>> libpng-1.6 hits the tree, or beforehand so that they will be
>> triggered for rebuild when libpng-1.6 hits.
>>
>
>
> so we force two rebuilds instead of one ?
>

Either we time it so they just rebuild at the same time (ie when the
package is unmasked or stable-keyworded), or we commit the revbump
earlier which would force a superfluous rebuild.

Technically there could (in theory at least) be a way of rewriting the
vdb to have the correct sub-slot entries (i had a script that did this
during my EAPI=4-slot-abi testing) but this isn't particularily safe
and would probably cause more issues for end users than the libpng-1.6
bump WITHOUT slot-operatored rdeps.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iF4EAREIAAYFAlFiChMACgkQ2ugaI38ACPBtYAD/YWxxprE1szh2meJVBt16Q+8x
it+AvHEbMiRetCHchoUA/R0Nkw0Tg6zrx0jO/RgA5U4/H6GGWZUO27VYz8TFu5ae
=yIRc
-----END PGP SIGNATURE-----

Reply | Threaded
Open this post in threaded view
|

Re: libpng 1.6 upgrade and subslotting (and misuse of subslotting when there is also normal slotting)

Ian Stakenvicius-2
In reply to this post by Ciaran McCreesh-4
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 06/04/13 11:27 AM, Ciaran McCreesh wrote:



I concurr.  Plus it was decided a couple of months back that everyone
should revbump or version bump when migrating to EAPI5 (if not all
future EAPIs).

The main issue, as I recall, with libpng system updates is that a
regular system-update-and-revdep-rebuild tends to fail because
packages need to be rebuilt during the middle of the system update.
Although this IS manageable even for green end-users with a bit of
hand-holding, ideally we want to avoid it as much as possible.


AFAICT, it's just a matter of timing the migration of rdeps we bump to
EAPI5 and slot-operator deps.  If we wanted to, we could:

1. revbump-and-p.mask ~arch packages, and the unmask them all when
libpng-1.6 is unmasked -- a common, grep'able comment in p.mask could
be used to indicate this list of package atoms.

2. ~arch-keyword a revbump of stable packages, and mass-stabilize when
libpng-1.6 goes stable.  A tracker bug would probably be best for this.

And of course, if the package has an update for other reasons in the
meantime, then they can just hit the tree as per normal and be removed
from the list(s) above.

Thoughts?


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iF4EAREIAAYFAlFiEJIACgkQ2ugaI38ACPCmWAD/UPXBQd0JwmK++UeZKfbaUK6w
tBkv+9sGVkQoJ3rGMfwA/ivRzMbrKJFoLH7TAsi0lGvIL4AQrgkVVv02oFKgRpaP
=u0Qx
-----END PGP SIGNATURE-----

Reply | Threaded
Open this post in threaded view
|

Re: libpng 1.6 upgrade and subslotting (and misuse of subslotting when there is also normal slotting)

Sergey Popov
In reply to this post by Samuli Suominen-4
06.04.2013 00:44, Samuli Suominen wrote:
> $ grep -r 'media-libs/libpng' */*/*.ebuild |grep -v ':.*='
> output -> http://bpaste.net/show/89268/

Thanks. app-admin/logstalgia and x11-wm/compiz are fixed.

--
Best regards, Sergey Popov
Gentoo Linux Developer
Desktop-effects project lead


signature.asc (567 bytes) Download Attachment