Skip to content

Bump to 9#950

Open
danirabbit wants to merge 7 commits intodeb-packagingfrom
danirabbit/packaging-granite9
Open

Bump to 9#950
danirabbit wants to merge 7 commits intodeb-packagingfrom
danirabbit/packaging-granite9

Conversation

@danirabbit
Copy link
Member

Goes with #949

@danirabbit danirabbit requested a review from a team February 10, 2026 21:52
@danirabbit danirabbit added this to OS 9 Feb 10, 2026
@danirabbit danirabbit moved this to Needs Review in OS 9 Feb 10, 2026
Copy link
Member

@ryonakano ryonakano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also I have a question: is there any reason you didn't modified debian/control?

@danirabbit danirabbit requested a review from ryonakano February 17, 2026 16:28
@danirabbit
Copy link
Member Author

@ryonakano looks like I accidentally didn't commit that file 😅 Thanks for noticing!

Copy link
Member

@ryonakano ryonakano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I got the following error when I build .deb files from this PR and #949:

user@elementary-test:~/work/granite$ debuild -us -uc
 dpkg-buildpackage -us -uc -ui
dpkg-buildpackage: info: source package granite7
dpkg-buildpackage: info: source version 7.8.0
dpkg-buildpackage: info: source distribution jammy
dpkg-buildpackage: info: source changed by elementary, Inc. <builds@elementary.io>
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture arm64
dpkg-source: error: source package has two conflicting values - granite9 and granite7
dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 25
debuild: fatal error at line 1184:
dpkg-buildpackage -us -uc -ui failed
user@elementary-test:~/work/granite$

Adding a new changelog for the new package name results build succeeded.

user@elementary-test:~/work/debian$ git diff
diff --git a/debian/changelog b/debian/changelog
index 058e9a2e..9ff5cae2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+granite9 (9.0.0) resolute; urgency=medium
+
+  * Release 9.0.0
+
+ -- Ryo Nakano <ryonakaknock3@gmail.com>  Sat, 21 Feb 2026 08:07:54 +0900
+
 granite7 (7.8.0) jammy; urgency=medium
 
   * Release 7.8.0 (#946)
user@elementary-test:~/work/debian$ 

Probably we need to add it now and then modify the release datetime when we finally release Granite 9 to make sure the same build error won't happen on Launchpad?

@ryonakano ryonakano mentioned this pull request Feb 20, 2026
Copy link
Member

@ryonakano ryonakano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I confirmed installing the following .deb files built with debuild -us -uc on a fresh OS Early Access succeeds.

gir1.2-granite-9.0_9.0.0_arm64.deb
granite-9-demo_9.0.0_arm64.deb
libgranite9_9.0.0_arm64.deb
libgranite-9-common_9.0.0_all.deb
libgranite-9-dev_9.0.0_arm64.deb

After that, I also confirmed the following snippet that uses Granite classes builds successfully with valac --pkg gtk4 --pkg granite-9 test.vala and runs as expected:

public class MyApp : Gtk.Application {
    public MyApp () {
        Object (
            application_id: "io.github.yourusername.yourrepositoryname",
            flags: ApplicationFlags.DEFAULT_FLAGS
        );
    }

    protected override void activate () {
        Granite.init();

        var label = new Granite.HeaderLabel ("Hello Again World!");

        var main_window = new Gtk.ApplicationWindow (this) {
            child = label,
            default_height = 300,
            default_width = 300,
            title = "Hello World"
        };
        main_window.present ();
    }

    public static int main (string[] args) {
        return new MyApp ().run (args);
    }
}
Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Needs Review

Development

Successfully merging this pull request may close these issues.

2 participants