#3461 custom tag/build-target for kde stack updates
Closed: Fixed None Opened 14 years ago by rdieter.

when last the kde-sig used normal buildroot overrides for a kde-stack update, there seemed to be a lot of confusion and errors made from other maintainers. It's been suggested a couple of times to use custom tags/build-target for this.

there's a kde-4.4.1 update on the works, so was wondering if the kde-sig could try this potentially safer method this time around.

dgilmore also suggested that the new tag use chain-builds too (I assume by self-poplulating, to avoid explicit overrides).

what do others think (worth it or not)?


I'm fine with it. Users will have to remember to add a --target option to the koji call, or KOJI_FLAGS="--target dist-f??-kde" to the make calls.

The first repo creation for this new tag will be costly, and will continue to have some cost on the system, so ask for it ahead of time, but not too far ahead of time.

I'm fine with it. Users will have to remember to add a --target option to the koji call, or KOJI_FLAGS="--target dist-f??-kde" to the make calls.

The first repo creation for this new tag will be costly, and will continue to have some cost on the system, so ask for it ahead of time, but not too far ahead of time.

cool, we'd like to get started using such asap for kde-4.4.1 landing soon.

What kind of time frame to implement it?

cool, we'd like to get started using such asap for kde-4.4.1 landing soon.

What kind of time frame to implement it?

Well it takes a couple minutes to setup the tags, and a couple hours probably for the newRepo to finish, and then it'll be ready.

What releases will 4.4.1 be landing in?

Well it takes a couple minutes to setup the tags, and a couple hours probably for the newRepo to finish, and then it'll be ready.

What releases will 4.4.1 be landing in?

ping? (the troops are getting restless)

ping? (the troops are getting restless)

dist-f1{1,2,3}-kde411 has been created as a build target and collection tag. Anything built into one of those tags will get added to the buildroot for those tags. They inherit from dist-f1{1,2}-updates and dist-f13 respectively.

http://koji.fedoraproject.org/koji/taskinfo?taskID=2033857

http://koji.fedoraproject.org/koji/taskinfo?taskID=2033863

http://koji.fedoraproject.org/koji/taskinfo?taskID=2033868

are the initial newRepo tasks. Once those are done, building can commence.

Let me know if you run into any issues.

dist-f1{1,2,3}-kde411 has been created as a build target and collection tag. Anything built into one of those tags will get added to the buildroot for those tags. They inherit from dist-f1{1,2}-updates and dist-f13 respectively.

http://koji.fedoraproject.org/koji/taskinfo?taskID=2033857

http://koji.fedoraproject.org/koji/taskinfo?taskID=2033863

http://koji.fedoraproject.org/koji/taskinfo?taskID=2033868

are the initial newRepo tasks. Once those are done, building can commence.

Let me know if you run into any issues.

for posterity, what I ended up using first was doing:
make build TARGET=dist-f13-kde441
or
make chain-build CHAIN="..." TARGET==dist-f13-kde441

for posterity, what I ended up using first was doing:
make build TARGET=dist-f13-kde441
or
make chain-build CHAIN="..." TARGET==dist-f13-kde441

Login to comment on this ticket.

Metadata