Fedora Release Engineering meeting summary for 2017-04-10
by Mohan Boddu
======================================
#fedora-meeting-2: RELENG (2017-04-10)
======================================
Meeting started by mboddu at 14:31:12 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-2/2017-04-10/releng.2017...
.
Meeting summary
---------------
* init process (mboddu, 14:31:12)
* #6645 Make sure OSTree repos are sync'ed correctly after the masher
completes (mboddu, 14:38:20)
* LINK: https://pagure.io/releng/issue/6645 (mboddu, 14:38:28)
* mboddu will update the ticket and will remove the meeting keyword,
since there is nothing more to discuss about it. (mboddu, 14:44:07)
* #6600 Mock and sigined rawhides (mboddu, 14:44:59)
* LINK: https://pagure.io/releng/issue/6600 (mboddu, 14:45:07)
* nirik filed a koji RFE but it seems like its going to take a while
to get it fixed. (mboddu, 14:48:38)
* Reason: nirik filed a koji RFE, they couldn't get rpm to work, then
he filed a rpm RFE and rpm devs said that it's supported by the
format, but not any of the tools (mboddu, 14:49:50)
* #5886 need method for distributing urgent fixes... urgently (mboddu,
14:51:55)
* LINK: https://pagure.io/releng/issue/5886 (mboddu, 14:52:01)
* mboddu will ask in the ticket if anyone wants it anymore (mboddu,
15:07:20)
* #6746 Produce a slimmed-down compose whenever certain packages appear
in an update (mboddu, 15:07:52)
* LINK: https://pagure.io/releng/issue/6746 (mboddu, 15:07:59)
* mboddu will create a stake holders(releng, infra and QA) meeting to
discuss more about it (mboddu, 15:16:41)
* Alternative Architectures updates (mboddu, 15:17:12)
* nirik is waiting on firewall changes and the instances are up and
running (mboddu, 15:19:21)
* Open Floor (mboddu, 15:19:54)
* Bodhi 2.5.0 is deployed in prod (mboddu, 15:24:13)
Meeting ended at 15:26:13 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* mboddu (57)
* nirik (35)
* maxamillion (12)
* masta (11)
* zodbot (8)
* bowlofeggs (5)
* Kellin (2)
* puiterwijk (1)
* marc84 (1)
* sharkcz (1)
* tyll (0)
* pbrobinson (0)
* pingou (0)
* dgilmore (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
7 years, 1 month
[releng] Issue #5622: [RFE] Allow user to (create/)delete private branches
by Pavel Raiskup
praiskup added a new comment to an issue you are following:
``
> I trust the packagers that they would not do this intentionally but
> mistakes happen and people might have built packages from the wrong
> branch in the past. The commit needs to be preserved for compliance
> with the GPL license as far as I know.
Agreed -> the __commit__ needs to be preserved, and it will be ->
regardless whether you removed the __branch__ (alias to commit) or not.
> The information about the commits is in koji and the database, but there is no
> tool to easily git a list of all commit hashes for a package.
Koji gives us "list of builds", which means "list of git hashes". Once
you disable remote git's gc, on the git server you still can do
'git log <SHA_HASH>'. So nothing is really lost.
More, if there's 'cgit' running (for our dist-git there is cgit), then you can
reference remote <SHA_HASH> simply through web browser (even if that
hash isn't referenced by any refspec).
I think cgit/git is enough to not loose any important data.
> And then there would need to be a second tool that checks for a private
> branch of a package that there are no commits from the list only in the
> branch to be deleted.
This doesn't really matter. For example, I removed "deleted-branch" from
[1] but you still can see the commit [2] (which is not referenced by
branch anymore). That will work till the commit is garbage collected
(this is server-side configurable).
[1] https://github.com/praiskup/git-gc-test
[2] https://github.com/praiskup/git-gc-test/commit/f6798011beb10a0896e
Also, to get the list of commits - from [2] you could go "up" through
"parent" links.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/5622
7 years, 1 month
[releng] Issue #5622: [RFE] Allow user to (create/)delete private branches
by Till Maas
till added a new comment to an issue you are following:
``
I trust the packagers that they would not do this intentionally but mistakes happen and people might have built packages from the wrong branch in the past. The commit needs to be preserved for compliance with the GPL license as far as I know.
The information about the commits is in koji and the database, but there is no tool to easily git a list of all commit hashes for a package. And then there would need to be a second tool that checks for a private branch of a package that there are no commits from the list only in the branch to be deleted.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/5622
7 years, 1 month