On 02/01/2016 11:44 PM, Jacco Ligthart wrote:
> On 02/01/2016 12:39 PM, Gordan Bobic wrote:
>> On 2016-01-31 23:03, Jacco Ligthart wrote:
>>> As some of you noticed, Redsleeve 6 is getting a bit behind with
>>> updates.
>>>
>>> A while ago I made a complete set called 6.7. The idea was to drop some
>>> old-and-not-used-anymore packages and create a complete set, in line
>>> with the latest from upstream. This has not made it into a release yet,
>>> the last show stopper is us not being able to build the latest firefox
>>> for it.
>>>
>>> Question: what shall I do with the updates? create an update tree next
>>> to the current 6.7 or fold them into the current 6.7 tree, as it is
>>> still unreleased?
>> If 6.7 base really is just 6.7 upstream release base, keep the updates
>> separate. If what we have tagged as 6.7 is 6.7 plus some updates anyway,
>> just fold the updates in, and deduplicate packages (only keep the latest
>> version if the latest version works).
> It has all updates till October 1st. as the release date was end of
> July, there are indeed some updates already in 6.7. I'll fold the new
> updates in.
>>
>> It would be nice to reduce all of EL6 to just one deduplicated repository
>> and archive off the rest.
> indeed that was the goal.
>
>>> (it might take a couple of days before all is build. It is now happily
>>> building libreoffice :) )
>> Yeah, that takes a day or two even with decent hardware.
>>
>>
OK, I think I'm complete with 6.7 updates till today. It should all be
on the mirrors soon.

small guide to my strange file/folder layout:
there are a couple of folders:
base - everything originally in RS6 base (build by Gordan)
update - everything originally in RS6 update (build by Gordan)
updates-testing - everything originally in RS6 updates-testing (build
and signed by me)
new - everything new in RS6.7 (build and signed by me)
old - stuff that should have been replace by a newer version, but I
could not get the newer version to build

RPM-GPG-KEY-redsleeve-6-testing the public part of the testing signing key
RS6.7_issuelog.html a log/guide to all the patches and errors I did/have
seen. (this should be merged with the issues in base/update)

for the new stuff I moved all the debuginfo to a separate debuginfo
folder. for all the other folders debug info should already be somewhere
else.

for updates-testing and new there are folders with patches I did.

Jacco

_______________________________________________
users mailing list
[email protected]
https://lists.redsleeve.org/mailman/listinfo/users

Reply via email to