All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pauli Virtanen <pav@iki.fi>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	Bastien Nocera <hadess@hadess.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v7 0/9] Functional/integration testing
Date: Fri, 11 Sep 2026 19:08:52 +0300	[thread overview]
Message-ID: <32f2cdeea1561dce8a974196bebbdd1b688e4542.camel@iki.fi> (raw)
In-Reply-To: <CABBYNZKW=W8_Q+KXmGmn9gt7hN74H_EO0mSd2vOzqM64yoGWmg@mail.gmail.com>

Hi,

to, 2026-09-10 kello 13:47 -0400, Luiz Augusto von Dentz kirjoitti:
[clip]
> While chatting with @Bastien Nocera he suggested moving
> https://github.com/pv/bluez-ci-image/ under bluez organization to make
> it easier to manage. Perhaps the same should happen for
> https://github.com/pv/pytest-bluezenv.
> 
> There is some documentation on how to do it, if you agree, on:
> https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository

The plan was that bluez-ci-image would be moved under bluez org. Image
name needs to be updated in the workflow scripts for the image and
action-ci, see
https://github.com/bluez/action-ci/pull/7#issue-4699895038

> There is some documentation on how to do it, if you agree, on:
>
https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository

This appears to require I'm member of the bluez org, as it complains I
don't have permissions to create public repositories there.

***

pytest-bluezenv would need BlueZ organization account on pypi.org so
releases can be done,

https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/#trusted-publishing

-- 
Pauli Virtanen

  reply	other threads:[~2026-09-11 16:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-06 16:49 [PATCH BlueZ v7 0/9] Functional/integration testing Pauli Virtanen
2026-09-06 16:49 ` [PATCH BlueZ v7 1/9] doc: add functional/integration testing documentation Pauli Virtanen
2026-09-06 18:29   ` Functional/integration testing bluez.test.bot
2026-09-06 16:49 ` [PATCH BlueZ v7 2/9] test: add functional/integration testing framework Pauli Virtanen
2026-09-06 16:49 ` [PATCH BlueZ v7 3/9] build: add functional testing target Pauli Virtanen
2026-09-06 16:49 ` [PATCH BlueZ v7 4/9] test: functional: impose Python code formatting Pauli Virtanen
2026-09-06 16:49 ` [PATCH BlueZ v7 5/9] test: functional: add some Agent1 interface tests Pauli Virtanen
2026-09-06 16:49 ` [PATCH BlueZ v7 6/9] test: functional: add basic obex file transfer tests Pauli Virtanen
2026-09-06 16:49 ` [PATCH BlueZ v7 7/9] test: functional: add tests running the various kernel testers Pauli Virtanen
2026-09-06 16:49 ` [PATCH BlueZ v7 8/9] test: functional: add test for adv_monitor crash Pauli Virtanen
2026-09-06 16:49 ` [PATCH BlueZ v7 9/9] test: functional: add test for AVRCP crash Pauli Virtanen
2026-09-08 17:48 ` [PATCH BlueZ v7 0/9] Functional/integration testing Luiz Augusto von Dentz
2026-09-08 18:33   ` Pauli Virtanen
2026-09-08 19:20 ` patchwork-bot+bluetooth
2026-09-09 18:56   ` Luiz Augusto von Dentz
2026-09-10 17:47     ` Luiz Augusto von Dentz
2026-09-11 16:08       ` Pauli Virtanen [this message]
2026-09-11 16:31         ` Luiz Augusto von Dentz
2026-09-11 17:04           ` Pauli Virtanen
2026-09-08 20:00 ` patchwork-bot+bluetooth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=32f2cdeea1561dce8a974196bebbdd1b688e4542.camel@iki.fi \
    --to=pav@iki.fi \
    --cc=hadess@hadess.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.