[gentoo-dev] NEW: split portage/repoman releases now in the tree

[gentoo-dev] NEW: split portage/repoman releases now in the tree

[Brian Dolbec]

portage-2.3.0_rc1 and repoman-2.3.0_rc1 are now in the tree.

portage-2.3.0_rc1 is essentially the portage 2.2.28 release with only a
few small patches applied.  It mostly just installs less code, namely
the repoman code.

So, now servers and other systems that do not require repo Q/A ability
will no longer get repoman installed anyway.

repoman-2.3.0_rc1 is the stage2 rewrite code. The checks are now
modular, and using the portage plugin system. The system is not yet
fully plug and play. Those changes will take place in the stage3
re-writes.

The two packages will remain in the same portage git repo, although the
repoman code has been moved into it's own pkg directory.  It is too
tied into portage api's to be on it's own just yet.  An that
is not likely to happen until we get a stable portage API.  This new
system does allow for semi-independant releases for both repoman and
portage.  When important API's change, it will require both to be
release at the same time.  So you can look forward to seeing the minor
version number to get more frequent bumps than it has this last decade.

Currently, the portage ebuild does not RDEPEND on the repoman ebuild.
You will have to explicitly emerge it for it to be installed. It has
been suggested to add a use flag enabled RDEPEND (default on) for the
dev profile.  I will also be adding that to the portage-9999 release
for all profiles in the coming days.

NOTES:  Repoman now depends on lxml for it's xml parsing and error
checking along with now using metadata.xsd.  It now will report a lot
more errors than the previous buggy code everyone has been using.

I want to thank the following people for their help and contributions
to make these releases:

	Zac Medico <zmedico>
	Alexander Bernsten <bernalex>
	Dirkjan Ochtman <djc> for the base xml re-write code
	Michal Gorny <mgorny> for the metadata.xsd changes
	Göktürk Yüksek <gokturk> for the metadata.xml test ebuilds
		patches.
	Mike Gilbert <floppym> for all the testing on the rewite code,
		and a number of gen-b0rk repo test ebuilds.
	
	Coacher for the recent testing, bug reports and patches.
	And anyone else I missed ;)

So, please report any issues with either the ebuilds or installs, bugs,
etc... you know the drill ;)

Don't forget, please contribute more test case ebuilds to the gen-b0rk
repo.  The better the test ebuild coverage we have, the better our Q/A
tools (like repoman) will be and the less often things will be released
broken.

Thank you
-- 
Brian Dolbec <dolsen>

Re: [gentoo-dev] NEW: split portage/repoman releases now in the tree

[Dirkjan Ochtman]

On Mon, May 16, 2016 at 3:39 AM, Brian Dolbec <dolsen@gentoo.org> wrote:
> repoman-2.3.0_rc1 is the stage2 rewrite code. The checks are now
> modular, and using the portage plugin system. The system is not yet
> fully plug and play. Those changes will take place in the stage3
> re-writes.

Thanks for working on this, it sounds great!

Cheers,

Dirkjan

Re: [gentoo-dev] NEW: split portage/repoman releases now in the tree

[Sam Jorna]

[-- Attachment #1: Type: text/plain, Size: 777 bytes --]

On Sun, May 15, 2016 at 06:39:22PM -0700, Brian Dolbec wrote:
> 
> portage-2.3.0_rc1 and repoman-2.3.0_rc1 are now in the tree.
 
> I want to thank the following people for their help and contributions
> to make these releases:
> 
> 	Zac Medico <zmedico>
> 	Alexander Bernsten <bernalex>
> 	Dirkjan Ochtman <djc> for the base xml re-write code
> 	Michal Gorny <mgorny> for the metadata.xsd changes
> 	Göktürk Yüksek <gokturk> for the metadata.xml test ebuilds
> 		patches.
> 	Mike Gilbert <floppym> for all the testing on the rewite code,
> 		and a number of gen-b0rk repo test ebuilds.
> 	
> 	Coacher for the recent testing, bug reports and patches.
> 	And anyone else I missed ;)

Thank you to everyone involved! :)

-- 
Sam Jorna
GnuPG Key: D6180C26

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 951 bytes --]

Re: [gentoo-dev] NEW: split portage/repoman releases now in the tree

[M. J. Everitt]

[-- Attachment #1: Type: text/plain, Size: 3164 bytes --]

On 16/05/16 02:39, Brian Dolbec wrote:
> portage-2.3.0_rc1 and repoman-2.3.0_rc1 are now in the tree.
w00t :D
> portage-2.3.0_rc1 is essentially the portage 2.2.28 release with only a
> few small patches applied.  It mostly just installs less code, namely
> the repoman code.
>
> So, now servers and other systems that do not require repo Q/A ability
> will no longer get repoman installed anyway.
>
> repoman-2.3.0_rc1 is the stage2 rewrite code. The checks are now
> modular, and using the portage plugin system. The system is not yet
> fully plug and play. Those changes will take place in the stage3
> re-writes.
Sounds promising :]
> The two packages will remain in the same portage git repo, although the
> repoman code has been moved into it's own pkg directory.  It is too
> tied into portage api's to be on it's own just yet.  An that
> is not likely to happen until we get a stable portage API.  This new
> system does allow for semi-independant releases for both repoman and
> portage.  When important API's change, it will require both to be
> release at the same time.  So you can look forward to seeing the minor
> version number to get more frequent bumps than it has this last decade.
>
> Currently, the portage ebuild does not RDEPEND on the repoman ebuild.
> You will have to explicitly emerge it for it to be installed. It has
> been suggested to add a use flag enabled RDEPEND (default on) for the
> dev profile.  I will also be adding that to the portage-9999 release
> for all profiles in the coming days.
'repoman' use flag for portage? something I'll need to add, since I
don't make (proper) use of profiles ..
> NOTES:  Repoman now depends on lxml for it's xml parsing and error
> checking along with now using metadata.xsd.  It now will report a lot
> more errors than the previous buggy code everyone has been using.
Uh-oh, breakage alert .. you mean repoman now enforces more rules, I
like .. :D
> I want to thank the following people for their help and contributions
> to make these releases:
>
> 	Zac Medico <zmedico>
> 	Alexander Bernsten <bernalex>
> 	Dirkjan Ochtman <djc> for the base xml re-write code
> 	Michal Gorny <mgorny> for the metadata.xsd changes
> 	Göktürk Yüksek <gokturk> for the metadata.xml test ebuilds
> 		patches.
> 	Mike Gilbert <floppym> for all the testing on the rewite code,
> 		and a number of gen-b0rk repo test ebuilds.
> 	
> 	Coacher for the recent testing, bug reports and patches.
> 	And anyone else I missed ;)
>
> So, please report any issues with either the ebuilds or installs, bugs,
> etc... you know the drill ;)
>
> Don't forget, please contribute more test case ebuilds to the gen-b0rk
> repo.  The better the test ebuild coverage we have, the better our Q/A
> tools (like repoman) will be and the less often things will be released
> broken.
>
> Thank you
Great job to Brian and all the other contributors! Keep up the good work.

Did we find a mechanism to trap updates to the EAPI not being in sync
with portage updates necessarily (I found an edge case bug #577546 - zac
has already given some useful thoughts)?

MJE


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

Re: [gentoo-dev] NEW: split portage/repoman releases now in the tree

[Francesco Riosa]

[-- Attachment #1: Type: text/plain, Size: 2875 bytes --]

2016-05-16 3:39 GMT+02:00 Brian Dolbec <dolsen@gentoo.org>:

>
> portage-2.3.0_rc1 and repoman-2.3.0_rc1 are now in the tree.
>
> portage-2.3.0_rc1 is essentially the portage 2.2.28 release with only a
> few small patches applied.  It mostly just installs less code, namely
> the repoman code.
>
> So, now servers and other systems that do not require repo Q/A ability
> will no longer get repoman installed anyway.
>
> repoman-2.3.0_rc1 is the stage2 rewrite code. The checks are now
> modular, and using the portage plugin system. The system is not yet
> fully plug and play. Those changes will take place in the stage3
> re-writes.
>
> The two packages will remain in the same portage git repo, although the
> repoman code has been moved into it's own pkg directory.  It is too
> tied into portage api's to be on it's own just yet.  An that
> is not likely to happen until we get a stable portage API.  This new
> system does allow for semi-independant releases for both repoman and
> portage.  When important API's change, it will require both to be
> release at the same time.  So you can look forward to seeing the minor
> version number to get more frequent bumps than it has this last decade.
>
> Currently, the portage ebuild does not RDEPEND on the repoman ebuild.
> You will have to explicitly emerge it for it to be installed. It has
> been suggested to add a use flag enabled RDEPEND (default on) for the
> dev profile.  I will also be adding that to the portage-9999 release
> for all profiles in the coming days.
>
> NOTES:  Repoman now depends on lxml for it's xml parsing and error
> checking along with now using metadata.xsd.  It now will report a lot
> more errors than the previous buggy code everyone has been using.
>
> I want to thank the following people for their help and contributions
> to make these releases:
>
>         Zac Medico <zmedico>
>         Alexander Bernsten <bernalex>
>         Dirkjan Ochtman <djc> for the base xml re-write code
>         Michal Gorny <mgorny> for the metadata.xsd changes
>         Göktürk Yüksek <gokturk> for the metadata.xml test ebuilds
>                 patches.
>         Mike Gilbert <floppym> for all the testing on the rewite code,
>                 and a number of gen-b0rk repo test ebuilds.
>
>         Coacher for the recent testing, bug reports and patches.
>         And anyone else I missed ;)
>
> So, please report any issues with either the ebuilds or installs, bugs,
> etc... you know the drill ;)
>
> Don't forget, please contribute more test case ebuilds to the gen-b0rk
> repo.  The better the test ebuild coverage we have, the better our Q/A
> tools (like repoman) will be and the less often things will be released
> broken.
>
> Thank you
> --
> Brian Dolbec <dolsen>
>
>
> Thank you Brian and all the persons involved

[-- Attachment #2: Type: text/html, Size: 3475 bytes --]

Re: [gentoo-dev] NEW: split portage/repoman releases now in the tree

[Marcin Mirosław]

W dniu 16.05.2016 o 10:45, Dirkjan Ochtman pisze:
> On Mon, May 16, 2016 at 3:39 AM, Brian Dolbec <dolsen@gentoo.org> wrote:
>> repoman-2.3.0_rc1 is the stage2 rewrite code. The checks are now
>> modular, and using the portage plugin system. The system is not yet
>> fully plug and play. Those changes will take place in the stage3
>> re-writes.
> 
> Thanks for working on this, it sounds great!

But it doesn't sounds so great for every every user;)
https://bugs.gentoo.org/show_bug.cgi?id=583252

Re: [gentoo-dev] NEW: split portage/repoman releases now in the tree

[Brian Dolbec]

On Tue, 17 May 2016 08:50:25 +0200
Marcin Mirosław <marcin@mejor.pl> wrote:

> W dniu 16.05.2016 o 10:45, Dirkjan Ochtman pisze:
> > On Mon, May 16, 2016 at 3:39 AM, Brian Dolbec <dolsen@gentoo.org>
> > wrote:  
> >> repoman-2.3.0_rc1 is the stage2 rewrite code. The checks are now
> >> modular, and using the portage plugin system. The system is not yet
> >> fully plug and play. Those changes will take place in the stage3
> >> re-writes.  
> > 
> > Thanks for working on this, it sounds great!  
> 
> But it doesn't sounds so great for every every user;)
> https://bugs.gentoo.org/show_bug.cgi?id=583252
> 
> 
> 

There was a reason it was released as _rc1,  And it was fixed real
quick with _rc1-r1, it was a small easy fix.  Incidentally , the error
was in the portage code, not the new repoman code which your reply
above seems to indicate. For those of you that might have installed
_rc1, the easy fix is install repoman, then upgrade to _rc1-r1, then
unmerge repoman if you don't want it.

For those that may not know, _rc stands for release candidate, when
major changes are done. Code is often released as a release candidate to
shake out any missed change that might be needed but missed due to
configuration and other conditions on the developers systems.

Thank you to those that tested it quite thoroughly after I released it.
Including finding the fix right away :D

-- 
Brian Dolbec <dolsen>