GNU bug report logs - #76311
Request for merging "kernel-team" branch

Previous Next

To reply to this bug, email your comments to 76311 AT debbugs.gnu.org.
There is no need to reopen the bug first.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: guix-patches <at> gnu.org
Subject: Request for merging "kernel-team" branch
Date: Sat, 15 Feb 2025 15:00:11 -0500

I've just created the first ever 'kernel-team' branch:

https://git.savannah.gnu.org/cgit/guix.git/log/?h=kernel-team

For now, it only includes an update to the 'kexec-tools' package, which
causes thousands of rebuilds via its effect on 'elogind'.

Is there anything else that should go on this branch? 

Message #8 received at 76311 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: Leo Famulari <leo <at> famulari.name>
Cc: 76311 <at> debbugs.gnu.org, Christopher Baines <mail <at> cbaines.net>
Subject: Re: Request for merging "kernel-team" branch
Date: Mon, 28 Apr 2025 21:43:47 +0200

Hello Leo,

the kernel-team branch is now third in line, which means that it will be
processed by QA as soon as one of the other two will have been pushed to
master. So I have rebased it on the recent master commit
d47379b8dc6fb79bd9f06598ce567aec80194365 known to the data service.

Is there anything else you would like to add to this branch?

Andreas

Message #11 received at 76311 <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: Andreas Enge <andreas <at> enge.fr>
Cc: 76311 <at> debbugs.gnu.org, Christopher Baines <mail <at> cbaines.net>
Subject: Re: Request for merging "kernel-team" branch
Date: Wed, 30 Apr 2025 19:02:56 -0400

On Mon, Apr 28, 2025 at 09:43:47PM +0200, Andreas Enge wrote:
> Hello Leo,
> 
> the kernel-team branch is now third in line, which means that it will be
> processed by QA as soon as one of the other two will have been pushed to
> master. So I have rebased it on the recent master commit
> d47379b8dc6fb79bd9f06598ce567aec80194365 known to the data service.
> 

> Is there anything else you would like to add to this branch?

Thanks for notifying me! I'll do a survey of open patches and see if
anything else qualifies.

Message #14 received at 76311 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: Leo Famulari <leo <at> famulari.name>
Cc: 76311 <at> debbugs.gnu.org, Christopher Baines <mail <at> cbaines.net>
Subject: Re: Request for merging "kernel-team" branch
Date: Tue, 6 May 2025 11:58:41 +0200

Hello Leo,

I have just merged the tex-team branch, so QA should pick up kernel-team
next, which I have just rebased on the new master branch.

Please keep an eye on QA and feel free to merge if you think the branch
is ready; it looks as if qt-team, which is now just before kernel-team,
will need more time, and I assume the changes are independent anyway.

Andreas

Message #17 received at 76311 <at> debbugs.gnu.org (full text, mbox):

From: Z572 <z572 <at> z572.online>
To: Leo Famulari <leo <at> famulari.name>
Cc: 76311 <at> debbugs.gnu.org
Subject: Re: [bug#76311] Request for merging "kernel-team" branch
Date: Thu, 08 May 2025 20:28:39 +0800

[Message part 1 (text/plain, inline)]

Leo Famulari <leo <at> famulari.name> writes:

> I've just created the first ever 'kernel-team' branch:
>
> https://git.savannah.gnu.org/cgit/guix.git/log/?h=kernel-team
>
> For now, it only includes an update to the 'kexec-tools' package, which
> causes thousands of rebuilds via its effect on 'elogind'.
>
> Is there anything else that should go on this branch? 

i think bluez update should go to kernel-team branch
https://issues.guix.gnu.org/74597 

[signature.asc (application/pgp-signature, inline)]

Message #20 received at 76311 <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: Z572 <z572 <at> z572.online>
Cc: 74597 <at> debbugs.gnu.org, 76311 <at> debbugs.gnu.org,
 Julian Flake <flake <at> uni-koblenz.de>
Subject: Re: [bug#76311] Request for merging "kernel-team" branch
Date: Thu, 8 May 2025 20:40:44 -0400

On Thu, May 08, 2025 at 08:28:39PM +0800, Z572 wrote:
> i think bluez update should go to kernel-team branch
> https://issues.guix.gnu.org/74597 

I've added the bluez update to the kernel-team branch:

https://git.savannah.gnu.org/cgit/guix.git/log/?h=kernel-team

We can check it's progress here:

https://qa.guix.gnu.org/branch/kernel-team

Hopefully the QA service will pick up the changes on the branch and
build them for us. This is my first time participating in the team
branch QA process so I'm unfamiliar with the details.

Message #23 received at 76311 <at> debbugs.gnu.org (full text, mbox):

From: Z572 <z572 <at> z572.online>
To: Leo Famulari <leo <at> famulari.name>
Cc: 76311 <at> debbugs.gnu.org, Julian Flake <flake <at> uni-koblenz.de>
Subject: Re: [bug#76311] Request for merging "kernel-team" branch
Date: Sat, 10 May 2025 18:07:39 +0800

[Message part 1 (text/plain, inline)]

Leo Famulari <leo <at> famulari.name> writes:

> On Thu, May 08, 2025 at 08:28:39PM +0800, Z572 wrote:
>> i think bluez update should go to kernel-team branch
>> https://issues.guix.gnu.org/74597 
>
> I've added the bluez update to the kernel-team branch:
>
> https://git.savannah.gnu.org/cgit/guix.git/log/?h=kernel-team
>
> We can check it's progress here:
>
> https://qa.guix.gnu.org/branch/kernel-team
>
> Hopefully the QA service will pick up the changes on the branch and
> build them for us. This is my first time participating in the team
> branch QA process so I'm unfamiliar with the details.

maybe also need add a jobset on ci.guix. for now only have
kernel-updates on ci.guix, but this branch is "kernel-team".

[signature.asc (application/pgp-signature, inline)]

Message #26 received at 76311 <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: Z572 <z572 <at> z572.online>
Cc: 76311 <at> debbugs.gnu.org, Julian Flake <flake <at> uni-koblenz.de>
Subject: Re: [bug#76311] Request for merging "kernel-team" branch
Date: Sat, 10 May 2025 14:42:04 -0400

On Sat, May 10, 2025 at 06:07:39PM +0800, Z572 wrote:
> maybe also need add a jobset on ci.guix. for now only have
> kernel-updates on ci.guix, but this branch is "kernel-team".

Thanks for pointing that out. I don't know how the teams jobs are added
to CI. The strings "gnome-team" or "emacs-team", for example, do not
appear in maintenance.git.

Also, it looks like the builds on QA for the kernel-team have stalled
now. Does anyone know what that means?

Message #29 received at 76311 <at> debbugs.gnu.org (full text, mbox):

From: Christopher Baines <mail <at> cbaines.net>
To: Leo Famulari <leo <at> famulari.name>
Cc: Z572 <z572 <at> z572.online>, Julian Flake <flake <at> uni-koblenz.de>,
 76311 <at> debbugs.gnu.org
Subject: Re: [bug#76311] Request for merging "kernel-team" branch
Date: Sat, 10 May 2025 19:49:21 +0100

[Message part 1 (text/plain, inline)]

Leo Famulari <leo <at> famulari.name> writes:

> On Sat, May 10, 2025 at 06:07:39PM +0800, Z572 wrote:
>> maybe also need add a jobset on ci.guix. for now only have
>> kernel-updates on ci.guix, but this branch is "kernel-team".
>
> Thanks for pointing that out. I don't know how the teams jobs are added
> to CI. The strings "gnome-team" or "emacs-team", for example, do not
> appear in maintenance.git.
>
> Also, it looks like the builds on QA for the kernel-team have stalled
> now. Does anyone know what that means?

QA for once hasn't actually stalled, it's just busy submitting builds
for the core-packages-team branch.

Given there are so many builds for that branch, and it still looks to
require quite a bit of work (currently the ARM bootstrap is broken), I'd
suggest making a decision on whether the kernel-team changes should be
merged before or after core-packages-team. Personally I think it makes
sense to shuffle round the order so that kernel-team can be built and
merged while core-packages-team is being fixed.

[signature.asc (application/pgp-signature, inline)]

Message #32 received at 76311 <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: Christopher Baines <mail <at> cbaines.net>
Cc: Z572 <z572 <at> z572.online>, Julian Flake <flake <at> uni-koblenz.de>,
 76311 <at> debbugs.gnu.org
Subject: Re: [bug#76311] Request for merging "kernel-team" branch
Date: Sat, 10 May 2025 16:02:44 -0400

On Sat, May 10, 2025 at 07:49:21PM +0100, Christopher Baines wrote:
> QA for once hasn't actually stalled, it's just busy submitting builds
> for the core-packages-team branch.
> 
> Given there are so many builds for that branch, and it still looks to
> require quite a bit of work (currently the ARM bootstrap is broken), I'd
> suggest making a decision on whether the kernel-team changes should be
> merged before or after core-packages-team. Personally I think it makes
> sense to shuffle round the order so that kernel-team can be built and
> merged while core-packages-team is being fixed.

I'm optimistic that the changes on the 'kernel-team' branch are limited
enough in scope that things will work, and that it won't be a waste of
time to run its builds before that of the core-packages-team.

I'll rebuild my system based on it now, although I can only meaningfully
test the changes to kexec-tools, and not to bluez / Bluetooth.

Message #35 received at 76311 <at> debbugs.gnu.org (full text, mbox):

From: Christopher Baines <mail <at> cbaines.net>
To: Leo Famulari <leo <at> famulari.name>, control <at> debbbugs.gnu.org
Cc: Z572 <z572 <at> z572.online>, Julian Flake <flake <at> uni-koblenz.de>,
 75518 <at> debbugs.gnu.org, 76311 <at> debbugs.gnu.org
Subject: Re: [bug#76311] Request for merging "kernel-team" branch
Date: Sun, 11 May 2025 10:49:42 +0100

[Message part 1 (text/plain, inline)]

block 75518 by 76311
thanks

Leo Famulari <leo <at> famulari.name> writes:

> On Sat, May 10, 2025 at 07:49:21PM +0100, Christopher Baines wrote:
>> QA for once hasn't actually stalled, it's just busy submitting builds
>> for the core-packages-team branch.
>> 
>> Given there are so many builds for that branch, and it still looks to
>> require quite a bit of work (currently the ARM bootstrap is broken), I'd
>> suggest making a decision on whether the kernel-team changes should be
>> merged before or after core-packages-team. Personally I think it makes
>> sense to shuffle round the order so that kernel-team can be built and
>> merged while core-packages-team is being fixed.
>
> I'm optimistic that the changes on the 'kernel-team' branch are limited
> enough in scope that things will work, and that it won't be a waste of
> time to run its builds before that of the core-packages-team.

Ok, I've gone ahead and put core-packages-team behind kernel-team.

> I'll rebuild my system based on it now, although I can only meaningfully
> test the changes to kexec-tools, and not to bluez / Bluetooth.

Note that bluez looks to fail to build
https://data.qa.guix.gnu.org/gnu/store/8j5qlh703367i6lwmnfggsh2s7s5cwf8-bluez-5.79.drv

[signature.asc (application/pgp-signature, inline)]

Message #40 received at 76311 <at> debbugs.gnu.org (full text, mbox):

From: Z572 <zhengjunjie <at> iscas.ac.cn>
To: Leo Famulari <leo <at> famulari.name>
Cc: Z572 <z572 <at> z572.online>, Julian Flake <flake <at> uni-koblenz.de>,
 76311 <at> debbugs.gnu.org
Subject: Re: [bug#76311] Request for merging "kernel-team" branch
Date: Sun, 11 May 2025 21:43:08 +0800

[Message part 1 (text/plain, inline)]

Leo Famulari <leo <at> famulari.name> writes:

> On Sat, May 10, 2025 at 06:07:39PM +0800, Z572 wrote:
>> maybe also need add a jobset on ci.guix. for now only have
>> kernel-updates on ci.guix, but this branch is "kernel-team".
>
> Thanks for pointing that out. I don't know how the teams jobs are added
> to CI. The strings "gnome-team" or "emacs-team", for example, do not
> appear in maintenance.git.

I think someone with the certificate configured it on the ci.guix web page, but
I don't have.

>
> Also, it looks like the builds on QA for the kernel-team have stalled
> now. Does anyone know what that means?

[signature.asc (application/pgp-signature, inline)]

Message #43 received at 76311 <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: Christopher Baines <mail <at> cbaines.net>
Cc: Dariqq <dariqq <at> posteo.net>, 74597 <at> debbugs.gnu.org, Z572 <z572 <at> z572.online>,
 Julian Flake <flake <at> uni-koblenz.de>, 76311 <at> debbugs.gnu.org
Subject: Re: [bug#76311] Request for merging "kernel-team" branch
Date: Sun, 11 May 2025 12:29:39 -0400

[Message part 1 (text/plain, inline)]

On Sun, May 11, 2025 at 10:49:42AM +0100, Christopher Baines wrote:
> Note that bluez looks to fail to build
> https://data.qa.guix.gnu.org/gnu/store/8j5qlh703367i6lwmnfggsh2s7s5cwf8-bluez-5.79.drv

With the help of several people on #guix IRC, I pushed an amended bluez
patch co-authored by Dariqq:

https://git.savannah.gnu.org/cgit/guix.git/commit/?h=kernel-team&id=cf4f234f215355ad8b34bfd7e4551221838b0ed4

This bluez package now builds successfully. Bluetoothers, please test!

[signature.asc (application/pgp-signature, inline)]

Message #46 received at 76311 <at> debbugs.gnu.org (full text, mbox):

From: Greg Hogan <code <at> greghogan.com>
To: Leo Famulari <leo <at> famulari.name>
Cc: 76311 <at> debbugs.gnu.org, Christopher Baines <mail <at> cbaines.net>,
 Z572 <z572 <at> z572.online>, Dariqq <dariqq <at> posteo.net>, 74597 <at> debbugs.gnu.org,
 Julian Flake <flake <at> uni-koblenz.de>
Subject: Re: [bug#76311] Request for merging "kernel-team" branch
Date: Sun, 11 May 2025 15:00:31 -0400

Are we ungrafting eudev on the kernel-team branch? The replacement was
only added recently.

Message #49 received at 76311 <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: Greg Hogan <code <at> greghogan.com>
Cc: Dariqq <dariqq <at> posteo.net>, Z572 <z572 <at> z572.online>,
 Christopher Baines <mail <at> cbaines.net>, 76311 <at> debbugs.gnu.org,
 Julian Flake <flake <at> uni-koblenz.de>
Subject: Re: [bug#76311] Request for merging "kernel-team" branch
Date: Sun, 11 May 2025 16:32:19 -0400

On Sun, May 11, 2025 at 03:00:31PM -0400, Greg Hogan wrote:
> Are we ungrafting eudev on the kernel-team branch? The replacement was
> only added recently.

Thanks for pointing this out. It would be nice to ungraft it now.

Chris, how does the QA build farm react to changing the branch as often
as I have been, (a few times per day)? Does it cancel pending builds if
the branch is updated? Or does it continue to build out the old branch,
which would make it relatively costly? I want to know how to use the
build farm properly with the team branch workflow.

Changing the subject, it would be nice if grafts were committed along
with an ungrafting commit to the team branch that would be responsible
for the code, assuming such a team exists. That way they wouldn't be
missed like I did here.

Message #52 received at 76311 <at> debbugs.gnu.org (full text, mbox):

From: Christopher Baines <mail <at> cbaines.net>
To: Leo Famulari <leo <at> famulari.name>
Cc: Dariqq <dariqq <at> posteo.net>, Z572 <z572 <at> z572.online>,
 Julian Flake <flake <at> uni-koblenz.de>, Greg Hogan <code <at> greghogan.com>,
 76311 <at> debbugs.gnu.org
Subject: Re: [bug#76311] Request for merging "kernel-team" branch
Date: Mon, 12 May 2025 10:36:44 +0100

[Message part 1 (text/plain, inline)]

Leo Famulari <leo <at> famulari.name> writes:

> On Sun, May 11, 2025 at 03:00:31PM -0400, Greg Hogan wrote:
>> Are we ungrafting eudev on the kernel-team branch? The replacement was
>> only added recently.
>
> Thanks for pointing this out. It would be nice to ungraft it now.
>
> Chris, how does the QA build farm react to changing the branch as often
> as I have been, (a few times per day)? Does it cancel pending builds if
> the branch is updated? Or does it continue to build out the old branch,
> which would make it relatively costly? I want to know how to use the
> build farm properly with the team branch workflow.

pending builds are canceled if the branch is updated. The data service
does take some time to process revisions, so making small and frequent
changes to a branch can slow things down. The biggest factor at the
moment though is Git operations to fetch from Savannah hanging and
causing the data service to miss updates.

[signature.asc (application/pgp-signature, inline)]

Message #55 received at 76311 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: Leo Famulari <leo <at> famulari.name>
Cc: 76311 <at> debbugs.gnu.org, Christopher Baines <mail <at> cbaines.net>
Subject: Re: Request for merging "kernel-team" branch
Date: Mon, 12 May 2025 14:30:13 +0200

Hello,

since there appears to have occurred an r-team branch merge, I have rebased
kernel-team and pushed, on a commit known to the data service.

There is a build failure for libinfinity on all architectures, see e.g.
   https://bordeaux.guix.gnu.org/build/6f0c19b3-fc88-423b-aa59-948fad5ec50c/log
It speaks of certificates, so this may be just time related.
And its only dependent package is gobby; both look abandoned, so I
intend to file a removal request.

Andreas

Message #58 received at 76311 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: Leo Famulari <leo <at> famulari.name>
Cc: 76311 <at> debbugs.gnu.org, Christopher Baines <mail <at> cbaines.net>
Subject: Re: Request for merging "kernel-team" branch
Date: Mon, 12 May 2025 14:46:23 +0200

Am Mon, May 12, 2025 at 02:30:13PM +0200 schrieb Andreas Enge:
> There is a build failure for libinfinity on all architectures, see e.g.
>    https://bordeaux.guix.gnu.org/build/6f0c19b3-fc88-423b-aa59-948fad5ec50c/log
> It speaks of certificates, so this may be just time related.

Adding a commit from their repository, which modifies the validity of
the certificate used for the test, solved the problem; so I have pushed
this to master.

Andreas

Message #61 received at 76311 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: Leo Famulari <leo <at> famulari.name>
Cc: 76311 <at> debbugs.gnu.org, Christopher Baines <mail <at> cbaines.net>
Subject: Re: Request for merging "kernel-team" branch
Date: Tue, 13 May 2025 15:43:53 +0200

Hello,

the branch has been almost built, and I did not see major problems
anymore. Adding an ungrafting commit would restart the whole process
from scratch again. So at this point in time, I think it would be
preferable to push the branch to master, and then maybe do a separate
ungrafting round. The total build effort would now be the same, and it
would give the other teams a chance to get their changes in.

What do you think?

Andreas

Message #64 received at 76311 <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: Andreas Enge <andreas <at> enge.fr>
Cc: 76311 <at> debbugs.gnu.org, Christopher Baines <mail <at> cbaines.net>
Subject: Re: Request for merging "kernel-team" branch
Date: Tue, 13 May 2025 11:04:41 -0400

On Tue, May 13, 2025 at 03:43:53PM +0200, Andreas Enge wrote:
> the branch has been almost built, and I did not see major problems
> anymore. Adding an ungrafting commit would restart the whole process
> from scratch again. So at this point in time, I think it would be
> preferable to push the branch to master, and then maybe do a separate
> ungrafting round. The total build effort would now be the same, and it
> would give the other teams a chance to get their changes in.
> 
> What do you think?

Is the next branch (core-packages-team?) ready?

The graft that we would remove is eudev, and it would trigger 5252
builds per architecture. For ci.guix.gnu.org, that is not very much. I
can't estimate how long it would take for QA. If it would take 2 or 3
days, I would say that it's worth it.

As there is not an ungrafting team or branch, I'm skeptical that we
would remove these grafts anytime soon, and I think there is some
benefit to removing them. Applying the grafts on everybody's machines
all the time incurs a real cost in terms of storage, power consumption,
and time.

Message #67 received at 76311 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: Leo Famulari <leo <at> famulari.name>
Cc: 76311 <at> debbugs.gnu.org, Christopher Baines <mail <at> cbaines.net>
Subject: Re: Request for merging "kernel-team" branch
Date: Tue, 13 May 2025 17:32:31 +0200

Am Tue, May 13, 2025 at 11:04:41AM -0400 schrieb Leo Famulari:
> Is the next branch (core-packages-team?) ready?

No, but I expect games-updates to be next then, as QA currently handles
two branches in parallel. This should be ready.

> The graft that we would remove is eudev, and it would trigger 5252
> builds per architecture. For ci.guix.gnu.org, that is not very much. I
> can't estimate how long it would take for QA. If it would take 2 or 3
> days, I would say that it's worth it.

I do not know how long it would take either. If everything goes well,
it would be fast... I suppose we can wait two or three days.

Andreas

Message #70 received at 76311 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: Leo Famulari <leo <at> famulari.name>
Cc: 76311 <at> debbugs.gnu.org, Christopher Baines <mail <at> cbaines.net>
Subject: Re: Request for merging "kernel-team" branch
Date: Wed, 14 May 2025 11:08:33 +0200

Hello Leo,

somehow you were unlucky and rebased on a master commit that is unknown
to the data service, so that QA does not show a comparison before-after.

I have rebased on the latest commit with a green badge from here:
   https://data.qa.guix.gnu.org/repository/1/branch/master
so that we should get useful information at
   https://qa.guix.gnu.org/branch/kernel-team

Andreas

Message #75 received at 76311-done <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: Leo Famulari <leo <at> famulari.name>
Cc: Christopher Baines <mail <at> cbaines.net>, 76311-done <at> debbugs.gnu.org
Subject: Re: Request for merging "kernel-team" branch
Date: Thu, 15 May 2025 13:48:41 +0200

Am Wed, May 14, 2025 at 11:08:33AM +0200 schrieb Andreas Enge:
> so that we should get useful information at
>    https://qa.guix.gnu.org/branch/kernel-team

Well, the branch looked good, so I have pushed it to master and deleted it.
Thanks for seeing these updates through!

Andreas

Message #78 received at 76311 <at> debbugs.gnu.org (full text, mbox):

From: Julian Flake <flake <at> uni-koblenz.de>
To: Leo Famulari <leo <at> famulari.name>
Cc: Dariqq <dariqq <at> posteo.net>, Z572 <z572 <at> z572.online>,
 Christopher Baines <mail <at> cbaines.net>, 76311 <at> debbugs.gnu.org,
 74597 <at> debbugs.gnu.org
Subject: Re: [bug#76311] Request for merging "kernel-team" branch
Date: Sat, 17 May 2025 09:06:29 +0200

[Message part 1 (text/plain, inline)]

Dear Leo,

On Sun, May 11 2025, Leo Famulari wrote:

> This bluez package now builds successfully. Bluetoothers, please 
> test!

Thanks for merging this already into master. Everything that 
worked before, still works, but my issue remains. However, the 
error message seems to have changed (now it's "Connection Failed: 
Operation already in progress bluez").

I couldn't find any other related upstream issue, yet. I probably 
will investigate further, when I find the time.

Since this issue's original subject was to update bluez to 5.79 , 
it can be closed now? Or should we leave it open, until my (and 
others') issue is resolved?

Best Regards,
nutcase

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.