CoreDevApplication

Differences between revisions 4 and 5
⇤ ← Revision 4 as of 2025-03-26 15:47:38 →
Size: 8181
Editor: hyask
Comment:
← Revision 5 as of 2025-05-17 15:55:03 → ⇥
Size: 10863
Editor: hyask
Comment:
Deletions are marked like this. Additions are marked like this.
Line 38: Line 38:
 * 2024-03-22 - Ubuntu Noble - [[https://launchpad.net/ubuntu/+source/pg-gvm/22.6.2-1build1|pg-gvm/22.6.2-1build1]]
 * 2024-03-21 - Ubuntu Noble - [[https://launchpad.net/ubuntu/+source/gvmd/23.1.0-1ubuntu1|gvmd/23.1.0-1ubuntu1]]
Line 43: Line 41:
* https://bugs.launchpad.net/ubuntu/+source/apt-clone/+bug/2106470
* https://bugs.launchpad.net/ubuntu/+source/beets/+bug/2106276
* https://bugs.launchpad.net/ubuntu/+source/beets/+bug/2107317 (https://salsa.debian.org/python-team/packages/beets/-/merge_requests/3)

CDimage stuff:
https://code.launchpad.net/~hyask/ubuntu-cdimage/+git/ubuntu-cdimage/+merge/484314
TODO: add also ubuntu-release-tools, ubuntu-archive-tools, etc...
Line 49: Line 54:
   * bug: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/2103526
Line 50: Line 56:
   * TODO: add description    * {{{base-files}}} upload for Noble .2
   * bug: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2097469
Line 52: Line 59:
   * TODO: add description    * SRU exception to update mirror list before release
   * bug: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2096775
Line 54: Line 62:
   * TODO: add description    * {{{base-files}}} upload for Oracular release, interestingly made without git ubuntu
   * bug: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2083825
Line 59: Line 68:
   * TODO: add description    * Just a boring merge
   * bug: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/2098852
Line 61: Line 71:
   * TODO: add description    * Interesting merge that needed to be coordinated with the next one in {{{util-linux}}}, because of the {{{login}}} binary package moving from one to the other.
   * bug: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2089923
Line 63: Line 74:
   * TODO: add description    * See {{{shadow}}} merge description just above.
   * bug: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2091862
Line 69: Line 81:
   * This one had an interesting story revolving around some Merge-O-Matic + mod_python + Python 3.9 madness.
Line 73: Line 86:
   * Pretty boring buffer overflow issue. One notable part is that this was apparently reported in 2018 as a CVE: https://nvd.nist.gov/vuln/detail/CVE-2018-13410
   * Submitted to Debian and uploaded
Line 90: Line 105:
* TODO: make some * TODO: make some more
 * 2024-03-22 - Ubuntu Noble - [[https://launchpad.net/ubuntu/+source/pg-gvm/22.6.2-1build1|pg-gvm/22.6.2-1build1]]
   * Infamous t64 transition
 * 2024-03-21 - Ubuntu Noble - [[https://launchpad.net/ubuntu/+source/gvmd/23.1.0-1ubuntu1|gvmd/23.1.0-1ubuntu1]]
   * Infamous t64 transition
Line 107: Line 126:
   * Normal MIR process for {{{retry}}} on Noble to get {{{autopkgtest}}} SRU'd too (new dependency).
Line 108: Line 128:
   * Same story here, except that it fall under the particular case of having {{{retry}}} only in the jammy-release pocket, so couldn't be updated. This required a new upload to reach jammy-updates and then get promoted to {{{main}}}.
Line 111: Line 132:
 * https://code.launchpad.net/~hyask/ubuntu-seeds/+git/ubuntu-seeds/+merge/483070
   * TODO: add description		  * 2025-03-19 - Ubuntu Plucky - https://code.launchpad.net/~hyask/ubuntu-seeds/+git/ubuntu-seeds/+merge/483070
   * Simple update of {{{ship-live}}} for ARM laptops
   * commit: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=1b5098bb6635bb1181faa8b5f1c6806b0aada26d
Line 118: Line 140:
 * {{{beets}}}:
   * Forwarded a bugfix: https://salsa.debian.org/python-team/packages/beets/-/merge_requests/3
   * Uploaded there: https://tracker.debian.org/news/1639271/accepted-beets-220-3-source-into-unstable/
Line 119: Line 144:
   * Forwarding a dep8 test for {{{util-linux}}}: https://salsa.debian.org/debian/util-linux/-/merge_requests/37
   * Subsequently patching this test after some feedback and discussion with zeha: https://salsa.debian.org/debian/util-linux/-/merge_requests/39		    * Forwarded a dep8 test for {{{util-linux}}}: https://salsa.debian.org/debian/util-linux/-/merge_requests/37
   * Subsequently patched this test after some feedback and discussion with @zeha (the Debian maintainer): https://salsa.debian.org/debian/util-linux/-/merge_requests/39
Line 122: Line 147:
   * This is closer to my regular work, so there are many MR that have been merged there already.    * This is closer to my regular work in Foundations, so there are many MR that have been merged there already.
Line 124: Line 149:
 * {{{zip}}}: forwarded a dep8 test + bugfix:
   * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093629		  * {{{zip}}}: forwarded a dep8 test + bugfix: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093629
   * Bugfix got uploaded: https://tracker.debian.org/news/1641790/accepted-zip-30-15-source-into-unstable/
   * Bigger plans for the test suite: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104090#17
Line 129: Line 155:
 * {{{beets}}}:
   * Forwarded a bugfix: https://github.com/beetbox/beets/pull/5708

I, Skia, hereby apply for core-dev.

Name

Florent 'Skia' Jacquet

Launchpad Page

https://launchpad.net/~hyask

Wiki Page

https://wiki.ubuntu.com/skia/


I am applying because:

  • I'd like to be able to officially join the Release Team.
  • I'd like to help smoothen the release process by being able to upload some bits by myself.
  • I'd like to be able to push some improvements to tools like MoM.

Who I am

This is almost plain copy-paste from my Contributing Developer application, given that the story hasn't changed.

My name is Florent Jacquet, but just call me Skia, even IRL, as everyone does.

I first installed Xubuntu 7.10 alternate edition on a 64MB RAM machine in 2008. The machine was already 10 years old by that time, but the lightweight system made it usable again, and it was great! Since then, I’ve installed a lot of {X,K,}Ubuntu on all my relative’s machines: parents, grand-parents, uncles, cousins, high-school companions, high school’s machines themselves, university friends and associations, you name it. I’ve personally distro-hoped for a while, but always kept either Debian or Ubuntu on my servers or machines that I wanted stable.

I now work since 2023-10-31 for Canonical as part of Foundations/Ubuntu QA/Release Management team.

My Ubuntu story

My involvement

Examples of my work / Things I'm proud of

* https://bugs.launchpad.net/ubuntu/+source/apt-clone/+bug/2106470 * https://bugs.launchpad.net/ubuntu/+source/beets/+bug/2106276 * https://bugs.launchpad.net/ubuntu/+source/beets/+bug/2107317 (https://salsa.debian.org/python-team/packages/beets/-/merge_requests/3)

CDimage stuff: https://code.launchpad.net/~hyask/ubuntu-cdimage/+git/ubuntu-cdimage/+merge/484314 TODO: add also ubuntu-release-tools, ubuntu-archive-tools, etc...

Feature upload

Package Merges and Syncs

Bug Fixes & SRUs

Autopkgtest & DEP8

* TODO: talk about rust-reqwest, util-linux, zip

Proposed Migrations

  • I'm regularly being affected packages stuck in proposed during Foundations' Thursday meetings. Working with those usually involves retriggering autopkgtest, sometimes finding the right triggers for the tests to pass, and more rarely a fix to be uploaded.

  • As part of my work on the autopkgtest infrastructure, I also regularly run retry-autopkgtest-regression for massive re-run of tests, sometimes involving shenanigans like adding a particular trigger for big sets of packages, or even running them with all-proposed=1.

Transitions

* TODO: make some more

Milestones and Exceptions

+1 maintenance

* TODO: make some

MIRs

  • 2024-09-18 - Ubuntu Noble - retry/1.0.5-3build1~ubuntu0.24.04.1

    • Normal MIR process for retry on Noble to get autopkgtest SRU'd too (new dependency).

  • 2024-09-16 - Ubuntu Jammy - retry/1.0.4-3build1

    • Same story here, except that it fall under the particular case of having retry only in the jammy-release pocket, so couldn't be updated. This required a new upload to reach jammy-updates and then get promoted to main.

Seed Operations

Working with upstream

Debian

Upstream projects

Misc

TODO

Bug Triage

  • Regular Foundations bug triage:
    • TODO: describe and link that work

Areas of work

Things I could do better

Plans for the future

General

What I like least in Ubuntu

Comments

If you'd like to comment, but are not the applicant or a sponsor, do it here. Don't forget to sign with @SIG@.

Endorsements

TEMPLATE

== <SPONSORS NAME> ==
=== General feedback ===
## Please fill us in on your shared experience. (How many packages did you sponsor? 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.''
## Full list of sponsored packages can be generated here:
##  https://udd.debian.org/cgi-bin/ubuntu-sponsorships.cgi
=== Areas of Improvement ===

CategoryCoreDevApplication

skia/CoreDevApplication (last edited 2025-11-24 15:17:54 by utkarsh)