Bug 1189698 - wsl-appx build differs between OBS and osc
Summary: wsl-appx build differs between OBS and osc
Status: NEW
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Other (show other bugs)
Version: Current
Hardware: Other All
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Jeff Kowalczyk
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 1081754
  Show dependency treegraph
 
Reported: 2021-08-22 12:28 UTC by Bernhard Wiedemann
Modified: 2021-08-23 04:47 UTC (History)
1 user (show)

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bernhard Wiedemann 2021-08-22 12:28:42 UTC
While working on reproducible builds for openSUSE, I found that
building our wsl-appx package with osc build
produced different results from the official OBS build.

+++ /usr/share/wsl-appx/AppxManifest.xml
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <Package IgnorableNamespaces="uap uap2 uap3 rescap desktop" xmlns="http://schem
as.microsoft.com/appx/manifest/foundation/windows10" xmlns:desktop="http://schem
as.microsoft.com/appx/manifest/desktop/windows10" xmlns:mp="http://schemas.micro
soft.com/appx/2014/phone/manifest" xmlns:rescap="http://schemas.microsoft.com/ap
px/manifest/foundation/windows10/restrictedcapabilities" xmlns:uap="http://schem
as.microsoft.com/appx/manifest/uap/windows10" xmlns:uap2="http://schemas.microso
ft.com/appx/manifest/uap/windows10/2" xmlns:uap3="http://schemas.microsoft.com/a
ppx/manifest/uap/windows10/3">
-    <Identity Name="46932SUSE.openSUSETumbleweed" ProcessorArchitecture="x64" Publisher="CN=15720A30-FA72-4BF5-8077-C1376E0B561C" Version="21153.0.0.0"/>
+    <Identity Name="46932SUSE.openSUSETumbleweed" ProcessorArchitecture="x64" Publisher="nobody" Version="21153.0.0.0"/>
     <Properties>
         <DisplayName>openSUSE Tumbleweed</DisplayName>
         <PublisherDisplayName>SUSE</PublisherDisplayName>


Is there a way to always get the Publisher field set?
Comment 1 Ludwig Nussel 2021-08-23 04:47:17 UTC
The publisher needs to match the signing certificate. If you want to reproduce that you'd have to create a fake _projectcert.crt that has the same CN as the official one. Obviously the signature would still not match.