Xpore Autopkgtest Review ( Bug #1035276 )

2023-12-29 Thread Komolehin Israel
Hi Team, I worked on the Xpore package by providing autopkgtest and embedding test data. CI was successful. This closes #1035276 bug. I look forward to its review and upload. Regards, Israel.

Re: Xpore Autopkgtest Review ( Bug #1035276 )

2023-12-29 Thread Nilesh Patra
Hi Israel, On Fri, Dec 29, 2023 at 01:01:47PM +0100, Komolehin Israel wrote: > I worked on the Xpore package by providing autopkgtest and embedding test > data. CI was successful. > > This closes #1035276 bug. > > I look forward to its review and upload. I have two comments: * Add in the copyr

Re: Xpore Autopkgtest Review ( Bug #1035276 )

2023-12-29 Thread Nilesh Patra
On Fri, Dec 29, 2023 at 05:57:13PM +0530, Nilesh Patra wrote: > Hi Israel, > > On Fri, Dec 29, 2023 at 01:01:47PM +0100, Komolehin Israel wrote: > > I worked on the Xpore package by providing autopkgtest and embedding test > > data. CI was successful. > > > > This closes #1035276 bug. > > > > I

Re: Xpore Autopkgtest Review ( Bug #1035276 )

2023-12-29 Thread Komolehin Israel
> On Fri, 29 Dec 2023 at 1:36 PM, Nilesh Patra wrote: > On Fri, Dec 29, 2023 at 05:57:13PM +0530, Nilesh Patra wrote: > > Hi Israel, > > > > On Fri, Dec 29, 2023 at 01:01:47PM +0100, Komolehin Israel wrote: > > > I worked on the Xpore package by providing autopkgtest and embedding > test > > > da

Re: Please help fixing meson/cmake code of btllib to use Debian packaged libargparse

2023-12-29 Thread Andreas Tille
Am Fri, Dec 29, 2023 at 11:35:41AM +0530 schrieb Nilesh Patra: > On a brief look, it does not seem easy and would mean maintaining a debian > specific > patch for ever which maybe non-trivial for future versions. > > Can we not support just the default python3-dev? Sure. Feel free to implement

Re: Last call for any other location than Berlin (Was: Any suggestions for next Debian Med sprint (in person meeting)?)

2023-12-29 Thread Andreas Tille
Am Wed, Dec 27, 2023 at 09:43:19PM +0100 schrieb Steffen Möller: > > for teaching and meeting reasons. > > > > But as I just wrote, 17-18 also works. > > I'd opt for the earlier date, so we have a bit of a break before some of us I > expect to bump into each other again in Hamburg if Holger's ev

[Advent bug squashing] Bugs from the past couple weeks

2023-12-29 Thread Lin Qigang
Hi, Here are some bugs I completed during the past couple weeks that have not been shared: #1046603, #1049759, #1044021, #1049553, #1048254, #1049212, #1049762, #1047040, #1048502, #1058302. While I do not plan to close any more before the new year, I enjoyed joining this year's bug squashin

Re: [Advent bug squashing] Bugs from the past couple weeks

2023-12-29 Thread Andreas Tille
Hi Lance, Am Fri, Dec 29, 2023 at 10:36:54PM +0700 schrieb Lin Qigang: > While I do not plan to close any more before the new year, I enjoyed joining > this year's bug squashing advent. Thank you again to all of my sponsors and > those who offered help. It was a pleasure to work with you. In fut

Re: [Advent bug squashing] Bugs from the past couple weeks

2023-12-29 Thread Étienne Mollier
Hi all, Thanks Lin for the additional entries. I counted bug entries closed between December first and twenty fourth on the Debian Med Packaging Alioth mailing list[1], and there were 179 closed bugs. That is between 7 and 8 bugs closed per day, which is a non negligible fraction of the team's o

[Advent Bug Squashing] My bug fixes during advent calendar

2023-12-29 Thread Nilesh Patra
Hi, Instead of sending each bug fix mail to the list, I thought of sending a consolidated list instead, for the advent BSP, starting Dec 1. +--+--+---+ | #1058558 | seqkit | RC| +--+--+---+ | #1046668 | seqkit

Re: Please help fixing meson/cmake code of btllib to use Debian packaged libargparse

2023-12-29 Thread Nilesh Patra
On Fri, Dec 29, 2023 at 02:04:34PM +0100, Andreas Tille wrote: > Am Fri, Dec 29, 2023 at 11:35:41AM +0530 schrieb Nilesh Patra: > > On a brief look, it does not seem easy and would mean maintaining a debian > > specific > > patch for ever which maybe non-trivial for future versions. > > > > Can w