Application - ROCm Package Set - Talha Can Havadar

I, Talha Can Havadar, apply for upload rights for ROCm package-set.

And the creation of a new rocm package-set. Please see ROCm package-set section below for packages in the set.

Contact Information:

Name Talha Can Havadar
Launchpad Page https://launchpad.net/~tchavadar
Matrix username @tchavadar:matrix.org

I am applying because:

  • I’d like to eliminate delays in getting my work sponsored.
  • I’d like to reduce the burden on my sponsors.
  • I’d like to be able to sponsor work of others

Who I am

Hello, I am Talha, a software engineer who is working with Canonical as
of today. Due to nature of my job I am interacting with our partners’ technical
teams and working with software that is provided by variety of silicon and tech
companies.

One of my recent involvement is with ROCm in the light of our partnership with
AMD. Hence, my application for a new package-set for ROCm and upload-rights for
me for this new package-set.

My Ubuntu Story

Of course as like for most of the developers, my Ubuntu journey started way before my professional
life. But I got even more involved for recent 3/4 years.

Examples of my work

Areas of work

During my time in Canonical, I have worked with variety of people but I will be
listing the ones related to my application below:

  • Andreas Hasenack
  • Benjamin Drung
  • Dave Jones
  • Frank Heimes
  • Ken VanDine
  • Loic Minier
  • Sebastien Bacher
  • Simon Chopin

The names I listed above are the people who either reviewed or sponsored my work
to ubuntu more than one time. I learned a lot from them so I thought I had to
mention them in my application.

My work mostly involves things related to AMD ecosystem. My past experience is on
embedded systems and I was working with Xilinx (Xilinx is also AMD now) platforms
even before I started working at Canonical so if you look at the packages I touch
you will see Xilinx related packages there as well, this is the reason. After
partnership with ROCm I started working on ROCm packages as well, in which I was
able to practice, the things I learned from my mentor.

Benjamin, was my mentor during my early days of getting hyped to be ubuntu developer.
I especially wanted to thank him for patiently answering my questions :slight_smile:

Things I could do better

I could probably start contributing to ubuntu way earlier and try to get involved
with distro work. But I was aware of the responsibility that it requires once you
become an ubuntu developer and that kept me away from studying and applying for it.

I could’ve created more opportunities for me to practice my packaging knowledge but
wasn’t able to do so. The things once I learned, flew away and get rusted so I
am trying to catch up with the changes. Still fighting with watch files and copyright,
thank god we have man pages.

Plans for the future

General

I am planning to keep contributing rocm stack since I did some personal investments
on AMD GPUs in my homelab :slight_smile: But the developments in the area of AI, keeps my interest
high and I like to be involved in this journey as well.

What I like least in Ubuntu

Sometimes it is hard to use cutting-edge tools while relying on LTS. One of my
recent struggle for example watch file v5 changes. Well it is not available for
devscripts in noble so if you just want to change some tools to the latest version
you are stuck with traditional distro, dependency problems. (I know snaps would help)
But I usually opt for easier solutions like third-party packaging platforms in which they already have the version I need.
I like the stability of the Ubuntu but would love to have official way to easily mess with it.

ROCm Package Set

Please follow this email thread for more up to date information: Request to create new "rocm" package-set for resolute

I have gathered a list of packages here to show the impact of this package set: Ubuntu Pastebin

Endorsements and Comments

Please leave your endorsements and comments following the template below, it is much much appreciated!

## Sponsoring feedback

* Please fill us in on your shared experience.
  * How many packages did you sponsor? A list of sponsored packages can generated [via UDD here](https://udd.debian.org/cgi-bin/ubuntu-sponsorships.cgi)
  * How would you judge the quality?
  * How would you describe the improvements?
  * Do you trust the applicant?

## Specific experiences of working together

*Please add good examples of your work together, but also cases that could have handled better.*

## Areas of improvement and next steps

What is the journey you see ahead of the applicant, the next steps they should take, the next things they likely have to learn and the next mountains to climb?
2 Likes

I would like to support Talha’s application, although I don’t have any elevated rights myself.

He is an undeniable voice of knowledge when it comes to debian packages among many squads in Partner engineering, and he mentored me on packaging numerous times. I am confident acquiring these rights is something Talha is fully prepared for, and it will unblock many of his packaging efforts moving forward.

1 Like

I would also like to add my enthusiastic support to Talha’s application.

In the two years I’ve worked with him, he’s repeatedly demonstrated both exceptional technical expertise and delivery. His understanding of the whole stack in Ubuntu - from image building and embedded work to package building and Launchpad - have contributed greatly to my own understanding as well as many others. He’s also a very willing teacher and keen to share his knowledge with others. Some specific areas where I’ve seen Talha provide exceptional leadership:

  • Delivering patched Debian packages and Ubuntu ISOs targeting RISC-V
  • Co-developing a fpgad snap to enable FPGA integration on Ubuntu Core
  • Major contributions to automation tools for custom image building
  • ROCm package development
1 Like

I will echo my colleagues’ support for Talha’s submission. He is a driving force within Partner Engineering with more than enough experience to be trusted with elevated permissions. His work in ROCm has been impressive to say the least, and it will not make sense for sponsors to consistently spend cycles on this active project while we have someone perfectly capable of uploading himself.

1 Like

I had the chance of working with Talha in the Canonical Partner Engineering team for a few years. He was very agreeable to work with, careful in his delivery of new technical pieces, and keen to learn about new technologies. Whenever I gave reviews/technical feedback, he would promptly adjust to meet higher standards.

I would trust Talha to work on this package set; I would also expect him to continue diversifying after FPGA and GPU work to become a more generalist Ubuntu developer :slight_smile:

1 Like

Sponsoring feedback

Packages I sponsored:

Date Sponsor Sponsoree Package Version Distribution Bugs fixed Action
2026-01-15 14:09 Andreas Hasenack Talha Can Havadar rocm-llvm 7.1.0+dfsg-0ubuntu1 resolute upgrade
2026-01-20 10:02 Andreas Hasenack Talha Can Havadar rocr-runtime 7.1.0+dfsg-0ubuntu5 resolute 2138659
2026-01-20 14:14 Andreas Hasenack Talha Can Havadar rocm-llvm 7.1.0+dfsg-0ubuntu2 resolute 2138733
2026-01-23 09:09 Andreas Hasenack Talha Can Havadar rocfft 7.1.0-0ubuntu1 resolute 2134241 2139240 upgrade
2026-01-26 16:36 Andreas Hasenack Talha Can Havadar rocm-llvm 7.1.0+dfsg-0ubuntu3 resolute 2138906
2026-01-26 16:57 Andreas Hasenack Talha Can Havadar rocr-runtime 7.1.0+dfsg-0ubuntu6 resolute 2138659
2026-01-28 20:35 Andreas Hasenack Talha Can Havadar rocprim 7.1.0-0ubuntu3 resolute
2026-02-01 18:22 Andreas Hasenack Talha Can Havadar rocm-hipamd 7.1.0-0ubuntu2 resolute 2138791
2026-02-03 15:57 Andreas Hasenack Talha Can Havadar rocm-llvm 7.1.0+dfsg-0ubuntu4 resolute 2138906
2026-02-05 08:00 Andreas Hasenack Talha Can Havadar rocrand 7.1.0-0ubuntu1 resolute upgrade
2026-02-10 12:35 Andreas Hasenack Talha Can Havadar rocsolver 7.1.0-0ubuntu1 resolute 2134241 upgrade
2026-02-12 12:30 Andreas Hasenack Talha Can Havadar slurm-wlm 25.11.2-1ubuntu1 resolute 2141666
2026-02-13 22:42 Andreas Hasenack Talha Can Havadar ggml 0.9.6-4ubuntu1 resolute 2138963
  • All but one (slurm-wlm) are part of the ROCm stack.

I was already doing reviews of his changes while the development was happening in the ROCM-devel ppa .

The quality of these uploads has improved by leaps and bounds, when compared to the first ones done to the PPA.

What I think is more telling, though, is how Talha has handled the integration points with the Ubuntu archive, and Ubuntu processes.

Even without upload rights at all, Talha has had to understand so many aspects of Ubuntu development already. His uploads involved soname changes, NEW binary packages, NEW source packages, excuses analysis, autopkgtest analysis, even update_output.txt.

I give some examples below. That is what gives me confidence that not only can he be trusted with upload rights to this stack, but he also understands where the stack touches other Ubuntu packages, and the consequences of that.

Specific experiences of working together

The ROCm stack has a few particularities that are challenging, specially in this project of integrating them with Ubuntu.

It’s a somewhat self-contained package set, yes, but only to a certain extent. And I would like to call out here specific examples where the set touched Ubuntu at large, and how Talha handled this:

Architectures

The ROCm upstream project focuses primarily on the AMD64 architecture, understandably. But Ubuntu and Debian still build these packages for more architectures were possible. Recently upstream basically said that other architectures are a best-effort case, and, together with recent failures to build on ppc64el, this led to the request for removal of these binaries, both in Debian and in Ubuntu. Here Talha and the ROCm team had to delve in on how Ubuntu handles such removals, and discovered it wasn’t as simple as patching the Architectures line in d/control. I started asking for reverse dependency analysis each time an architecture was changed, and Talha jumped into the task. Not only did the PRs now had full reverse dependencies analysis, they also prompted other PRs where needed for such reverse dependencies: either removing the build there as well (more drastic and rare), or disabling a certain plugin only in that architecture so that we didn’t have to yank a whole tree of packages from the distro just because of ROCm. Other times even leaving the architecture in place and fixing the FTBFS .

Working with Debian and Upstream

Several times during the ROCm packaging effort, changes were made in the packaging that Talha forwarded upstream. The ggml@ppc64el case was quite interesting, because even after having discovered LTO was the cause, Talha still wasn’t happy with the investigation and pursued it further, involving upstream and debian with very good discussions in both places.

Proposed migration

The changes in the ROCm stack in this Resolute cycle are exercising all aspects of proposed migration, and Talha has had to learn the “dark secrets” of proposed migration:

  • update_output.txt: figuring out why uploads are stuck in the excuses report with no problems reported there. These uploads are mainly stuck because of the architecture changes.
  • NEW packages: the ROCm stack introduced quite a few NEW binaries from existing sources in this cycle. Sometimes due to soname changes, sometimes just packaging changes.
  • NEW sources: the amount of work behind a NEW source review presented itself via the llvm-toolchain-rocm NEW source review.

Compilers

The ROCm stack can be built with an upstream LLVM compiler, or a fork of that compiler maintained by AMD. Suffice it to say, switching between them surfaces a lot of complex build and dependency issues.

Packaging in general

Branches up for review have:

  • build samples in PPAs, with proposed enabled (target is resolute anyway)
  • autopkgtest runs when applicable/available
  • patches with DEP3 headers, and forwarded upstream and/or to debian where applicable

Areas of improvement and next steps

Talha knows a lot about Ubuntu development already. I think what is left is to gain more experience, and exercise those touching points between this package set, and the rest of Ubuntu.

1 Like

I an delighted to endorse Talha for upload rights of the ROCm package set. I’ve sponsored 4 packages, 2 NEW and 2 updates to existing packages. Talha was thorough and thoughtful in the process with great attention to detail. Talha was also very responsive and welcoming of feedback along the way. Not only do I believe Talha will benefit from having upload rights for the ROCm package set, I believe Ubuntu will benefit from Talha’s increased reach which I hope will grow beyond ROCm.

Specific experiences of working together

1 Like

While I haven’t worked with the ROCm package set myself, I have sponsored the following changes for Talha (all in the flash-kernel package):

Date Package Version Distribution Bugs fixed
2023-12-08 14:17 flash-kernel 3.107ubuntu4 noble 2037407
2024-01-15 10:38 flash-kernel 3.107ubuntu2.1 mantic 2037407
2024-01-15 10:44 flash-kernel 3.104ubuntu18 jammy 2037407
2024-02-29 15:32 flash-kernel 3.104ubuntu20 jammy 2054556

He was responsive to reviews, and carried out the changes requested diligently. Reading through Andreas’ extremely thorough review above, and some of the associated tickets, I would also be happy to endorse his application for upload rights on (a newly created) ROCm package set.

1 Like

I am very happy having the chance to endorse Talha, who is as Senior Engineer, and with that one of the corners stones in Partner Engineering.
Talha is always driving things to the better better and towards more automated, which I really appreciate, and I think even the larger PE department benefits from.
I can say that he is very open for constructive feedback and suggestions and picks those up swiftly, while being very responsive.
On top he handles unknown territory with care and asks for feedback and for best practices and in special and uncommon cases.
I appreciate very much working together with him.

While doing so I sponsored a few package uploads for him (and reviewed even more on top):

Date Sponsoree Package Version Distribution Bugs fixed Action
2024-04-22 Talha Can Havadar dfx-mgr 2023.2-0ubuntu1 noble 2048462 upgrade
2026-01-19 Talha Can Havadar pkg-rocm-tools 0.9.5ubuntu1 resolute 2138457
2026-01-20 Talha Can Havadar rocm-smi-lib 7.1.0-0ubuntu2 resolute 2138653
2026-01-20 Talha Can Havadar rocm-smi-lib 7.1.0-0ubuntu3 resolute 2138727

Talha has and gathered a lot of valuable experiences in regard to packaging (and beyond) and is sharing them not only in his ROCm squad, but also beyond - on a larger PE level - which I appreciate a lot!

In his current role as technical lead of the ROCm (Partner Engineering) project, he is predestined to achieve upload permissions for this specific package set.
This will not only for the benefit and growth for him personally, but also for the benefit of the department, Canonical engineering and Ubuntu as a whole.

Hence I fully support his application without any doubts (and the above comments and endorsements seem to agree on that).

1 Like