I think we should get DAFFODIL-2568, it just needs one more +1:

https://github.com/apache/daffodil/pull/675

Also, DAFFODIL-2583 has two +1's and I think is probably close to being merged:

https://github.com/apache/daffodil/pull/676

Other than those two and the one you mentioned, I don't know of any other blockers.

On 11/11/21 12:10 PM, Mike Beckerle wrote:
Answering my own question... It seems that this PR
https://github.com/apache/daffodil/pull/674 and ticket DAFFODIL-2580 are
blockers.

Any others?

On Thu, Nov 11, 2021 at 12:01 PM Mike Beckerle <[email protected]> wrote:

With this resolved are we now ready to create RC1 ?

On Thu, Nov 11, 2021 at 7:21 AM Steve Lawrence (Jira) <[email protected]>
wrote:


      [
https://issues.apache.org/jira/browse/DAFFODIL-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Steve Lawrence resolved DAFFODIL-2584.
--------------------------------------
     Resolution: Fixed

Fixed in commit 772826c9070dea10ac4340c321f1071bda6fd2d2

Release candiate container fails to build MSI
---------------------------------------------

                 Key: DAFFODIL-2584
                 URL:
https://issues.apache.org/jira/browse/DAFFODIL-2584
             Project: Daffodil
          Issue Type: Bug
          Components: Infrastructure
            Reporter: Steve Lawrence
            Assignee: Steve Lawrence
            Priority: Blocker
             Fix For: 3.2.0


The release candidate container setup installs a handful of packages
from the fedora repos without specifying a verisons, so Fedora package
updates can break our release process. This has happened–the MSI now fails
to build with the error:
{quote}
light.exe : error LGHT0182 : Cannot find the table definitions for the
'SecureObjects' table.  This is likely due to a typing error or missing
extension.  Please ensure all the necessary extensions are supplied on the
command line with the -ext parameter.
{quote}
Since this fails with building the MSI, which is done with Wine, this
is probably a wine update that broke things. We won't be able to do a
release until this is resolved.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)




Reply via email to