>>
>> [Petter Reinholdtsen]
>> > WHR, did you manage to get access to the
>> > https://salsa.debian.org/debian/mfiutil/ > project yet?
>>
>> [WHR]
>> > Not yet.
>>
>> Jérémy, is there something I should do here, or do you have it covered?
>
>
> Well, one is supposed to request access to a reposit
Le jeu. 10 oct. 2024 à 07:02, Petter Reinholdtsen a
écrit :
>
> [Petter Reinholdtsen]
> > WHR, did you manage to get access to the
> > https://salsa.debian.org/debian/mfiutil/ > project yet?
>
> [WHR]
> > Not yet.
>
> Jérémy, is there something I should do here, or do you have it covered?
Well,
[Petter Reinholdtsen]
> WHR, did you manage to get access to the
> https://salsa.debian.org/debian/mfiutil/ > project yet?
[WHR]
> Not yet.
Jérémy, is there something I should do here, or do you have it covered?
--
Happy hacking
Petter Reinholdtsen
[Petter Reinholdtsen]
> WHR, did you manage to get access to the
> https://salsa.debian.org/debian/mfiutil/ > project yet?
Not yet.
> Are there any improvements that deserve a new upload to the NEW queue?
For the program itself, I already have some enhancements planned, but
currently lacks free
WHR, did you manage to get access to the
https://salsa.debian.org/debian/mfiutil/ > project yet?
Are there any improvements that deserve a new upload to the NEW queue?
--
Happy hacking
Petter Reinholdtsen
Very good. I see from https://ftp-master.debian.org/new.html >
the upload succeded.
--
Happy hacking
Petter Reinholdtsen
Le mar. 10 sept. 2024 à 19:26, Petter Reinholdtsen a
écrit :
>
> So, lets upload? Jérémy, can you do it? Who got write access to the
> repo?
I move it to
salsa.debian.org/debian/mfiutil
and updated Vcs-* fields in debian/control.
@WHR could you request access to that project ?
Meantime I'm
So, lets upload? Jérémy, can you do it? Who got write access to the
repo?
--
Happy hacking
Petter Reinholdtsen
Le mar. 10 sept. 2024 à 15:27, WHR a écrit :
> [Jérémy Lal]
> > 1. Please use DEP-3 format for patches (missing at least Description,
> > Forwarded fields)
> > https://dep-team.pages.debian.net/deps/dep3/
> > Oddly lintian didn't pick that.
> >
> > 2. It would be nicer to have a debian/watch file
[Jérémy Lal]
> 1. Please use DEP-3 format for patches (missing at least Description,
> Forwarded fields)
> https://dep-team.pages.debian.net/deps/dep3/
> Oddly lintian didn't pick that.
>
> 2. It would be nicer to have a debian/watch file
Hi,
These has been imlemented on https://salsa.debian.org
[WHR]
> I just created a debian/watch file, available on Salsa; give it a
> review?
'uscan -v' is happy, then I guess it is good. :)
--
Happy hacking
Petter Reinholdtsen
[Petter Reinholdtsen]
> As far as I understand Appstream, it only need to be unique string.
> Given that it is a different code base, I suspect it should not use a
> org.freebsd ID.
Make sense. I will keep the current ID.
I just created a debian/watch file, available on Salsa; give it a review?
[WHR]
> I have fixed the issue to make the validation pass; please check the latest
> commit.
Look good. :)
> Or perhaps the rDNS name of the next level upstream can be used, eg.
> org.freebsd.base.mfiutil. What do you think?
As far as I understand Appstream, it only need to be unique string.
Gi
[Petter Reinholdtsen]
> Please bring up your view with the group maintaining the Appstream
> specification. As things stand right now, the Appstream metainfo XML
> parser require it, so for the hardware mapping to make it into the
> directory for use by isenkram and others, it need to be accepted
[WHR]
> I'm not very comfortable for using a rDNS name; because the TLD is
> subject to change. I already experienced a TLD change for my
> organization domain name; thankfully because I never used rDNS names
> in my programs, this isn't a big problem.
Please bring up your view with the group main
The 'control' file and the patch has been updated accordingly.
[Petter Reinholdtsen]
> E: rivoreo.mfiutil:3: cid-is-not-rdns rivoreo.mfiutil
> W: rivoreo.mfiutil:~: metainfo-filename-cid-mismatch
>
> ✘ Validation failed: errors: 1, warnings: 1, pedantic: 1
>
> The appstream XML parser
I forgot to mention how to validate the Appstream XML:
appstreamcli validate-tree debian/mfiutil
When I run it on the current salsa git content, I get these:
mfiutil.metainfo.xml
E: rivoreo.mfiutil:3: cid-is-not-rdns rivoreo.mfiutil
W: rivoreo.mfiutil:~: metainfo-filename-cid-misma
Very good to hear from you, Jérémy. Good catch on the patch format and
watch file. I had not noticed those.
I had a new look at the code, and found a typo:
diff --git a/debian/control b/debian/control
index e81ff95..f2e8fa6 100644
--- a/debian/control
+++ b/debian/control
@@ -19,7 +19,7 @@ De
Le mar. 10 sept. 2024 à 04:40, WHR a écrit :
> Hello.
>
> It seems no activtiy in a while. Any progress?
>
Oops, sorry, I just read that. I'm reading
https://salsa.debian.org/Low-power/mfiutil
1. Please use DEP-3 format for patches (missing at least Description,
Forwarded fields)
https://dep-te
Hello.
It seems no activtiy in a while. Any progress?
[Petter Reinholdtsen]
> I suspect the tool is ready to go into the NEW queue, but would like
> to hear from Jérémy on this.
Jérémy, did you have time to check out the code?
--
Happy hacking
Petter Reinholdtsen
[WHR]
> I would like to do so, but I don't think FreeBSD would accept the
> big-endian fixes, because neither their mfi(4) nor mrsas(4) driver
> supports big-endian hosts in first place.
I guess you might be right, but only way to find out is to try. No idea
if the driver is also available on Net
>> Good to know. What about passing code the other way? Among other
>> things, I notice there are lots of endian fixes in the Linux port that
>> are missing in the FreeBSD port. I guess it would be useful on big
>> endian FreeBSD machines.
>
> I would like to do so, but I don't think FreeBSD wo
[Petter Reinholdtsen]
> Good to know. What about passing code the other way? Among other
> things, I notice there are lots of endian fixes in the Linux port that
> are missing in the FreeBSD port. I guess it would be useful on big
> endian FreeBSD machines.
I would like to do so, but I don't th
[WHR]
> The only major update in FreeBSD source that's not included here, is
> the support of their mrsas(4) driver; which has been implemented in
> this port in a different way (which actually shares with the Linux
> support code).
>
> Of course I will merge more future improvements from FreeBSD f
> I suspect I lack a tag. There are no tags in my clone, so I suspect you
> forgot 'git push --tags'.
Yep.
> Btw, do you know if uptream is in contact with the FreeBSD maintainers
> of mfiutil? Look to me like there have been some updates on FreeBSD
> that are not inlcuded in the Linux port.
Th
[WHR]
> No, I havn't used this.
I tried building with 'gbp buildpackage --pristine-tar', but no success:
gbp:error: upstream/1.0.15-rivoreo-r1_rc-20240830-e8b284c is not a
valid treeish
I suspect I lack a tag. There are no tags in my clone, so I suspect you
forgot 'git push --tags'.
> I ha
> Is the idea to use git-buildpackage?
No, I havn't used this.
> Do you plan to use
> pristine-tar to be able to reproduce the orig.tar.gz file from the git
> repo? I notice there is no pristine-tar branch there now.
I have just created a pristine-tar delta for the newly released upstream
sour
>> I will finalize the first release by tomorrow, assuming no additional
>> issues
>> are found in the source tree.
>>
>> I have updated the Debian packaging repo to the latest upstream version:
>> https://salsa.debian.org/Low-power/mfiutil/-/tree/master/
>
> Good. Is the idea to use git-buildpac
[WHR]
> I will finalize the first release by tomorrow, assuming no additional issues
> are found in the source tree.
>
> I have updated the Debian packaging repo to the latest upstream version:
> https://salsa.debian.org/Low-power/mfiutil/-/tree/master/
Good. Is the idea to use git-buildpackage?
Hi.
I will finalize the first release by tomorrow, assuming no additional issues
are found in the source tree.
I have updated the Debian packaging repo to the latest upstream version:
https://salsa.debian.org/Low-power/mfiutil/-/tree/master/
[Petter Reinholdtsen]
> (Btw, how did you come up wit
[WHR]
> I have got an account at Salsa:
> https://salsa.debian.org/Low-power/
Good to hear. I suggest you make the git repo under your own user as a
start. We can look at moving the repo somewhere else later if it make
sense.
(Btw, how did you come up with that user name?)
--
Happy hacking
Pe
Hello.
I have got an account at Salsa:
https://salsa.debian.org/Low-power/
> [WHR]
>> None. I havn't started using git for it yet.
>
> Right. Salsa might be the best choice, then. Did you get any response
> from the Salsa admins?
They said to try register again. I'm waiting for account approval once again.
>> Uploaded at https://mentors.debian.net/package/mfiutil/
>
[WHR]
> None. I havn't started using git for it yet.
Right. Salsa might be the best choice, then. Did you get any response
from the Salsa admins?
> Uploaded at https://mentors.debian.net/package/mfiutil/
Look like the QA information list already got several suggestions for
improvements. In ad
>> [WHR]
>>> I'm asking for suggestion of any improvement that should be done in the
>>> non-Debian source tree. For example should the Makefile be having some
>>> more
>>> features, that would benefit the Debian build system and possibly others?
>>>
>>> In the case of this Makefile btw, I already
> [WHR]
>> I'm asking for suggestion of any improvement that should be done in the
>> non-Debian source tree. For example should the Makefile be having some
>> more
>> features, that would benefit the Debian build system and possibly others?
>>
>> In the case of this Makefile btw, I already have a
[WHR]
> I'm asking for suggestion of any improvement that should be done in the
> non-Debian source tree. For example should the Makefile be having some more
> features, that would benefit the Debian build system and possibly others?
>
> In the case of this Makefile btw, I already have a Debian pa
Hello.
I'm asking for suggestion of any improvement that should be done in the
non-Debian source tree. For example should the Makefile be having some more
features, that would benefit the Debian build system and possibly others?
In the case of this Makefile btw, I already have a Debian patch to
[WHR]
> However, I just received an email that notifys my account creating
> request was rejected, without explanation. Any idea for this?
I do not know the procedure for approval or rejections on salsa, but
would suspect it is simply an error, perhaps a spam protection process
gone wrong. Did yo
> Le mar. 27 août 2024 à 01:04, WHR a écrit :
>
>> > [WHR]
>> >> I was writing a new section for the man page today. I will commit this
>> >> patch by tomorrow. Thanks.
>> >
>> > Good. What is your timeline for getting the package into Debian? I
>> > suspect the deadline to make it to the next
> [WHR]
>> I was writing a new section for the man page today. I will commit this
>> patch by tomorrow. Thanks.
>
> Good. What is your timeline for getting the package into Debian? I
> suspect the deadline to make it to the next stable release is
> approaching very quickly. Do you need help wit
Le mar. 27 août 2024 à 01:04, WHR a écrit :
> > [WHR]
> >> I was writing a new section for the man page today. I will commit this
> >> patch by tomorrow. Thanks.
> >
> > Good. What is your timeline for getting the package into Debian? I
> > suspect the deadline to make it to the next stable rel
[WHR]
> I was writing a new section for the man page today. I will commit this
> patch by tomorrow. Thanks.
Good. What is your timeline for getting the package into Debian? I
suspect the deadline to make it to the next stable release is
approaching very quickly. Do you need help with making Deb
>
> I built and tested the source on a machine running testing, and it seem
> to work fine. According to the compiler there are some potential buffer
> overflows:
>
> gcc -I include -std=gnu99 -Wall -Wno-unused-value -Os -c -o mfi_drive.o
> mfi_drive.c
> mfi_drive.c: In function ‘mfi_pdstate’:
I built and tested the source on a machine running testing, and it seem
to work fine. According to the compiler there are some potential buffer
overflows:
gcc -I include -std=gnu99 -Wall -Wno-unused-value -Os -c -o mfi_drive.o
mfi_drive.c
mfi_drive.c: In function ‘mfi_pdstate’:
mfi_drive.c:1
[Jérémy Lal]
> Since Peter and I put megactl in debian recently, it would make sense
> we help you on this one.
> It would be nice to maintain the debianization at
> https://salsa.debian.org/debian/mfiutil
> I can create the repo if needed.
It seem like a nice tool, indeed. I hope the package wil
Le dim. 25 août 2024 à 20:36, WHR a écrit :
> Package: wnpp
> Severity: wishlist
> Owner: WHR
> X-Debbugs-Cc: debian-de...@lists.debian.org, w...@rivoreo.one
>
> * Package name: mfiutil
> Version : 1.0.15-rivoreo-r1
> Upstream Contact: WHR
> * URL : https://sourcefor
Package: wnpp
Severity: wishlist
Owner: WHR
X-Debbugs-Cc: debian-de...@lists.debian.org, w...@rivoreo.one
* Package name: mfiutil
Version : 1.0.15-rivoreo-r1
Upstream Contact: WHR
* URL : https://sourceforge.net/projects/mfiutil/
* License : BSD-3-Clause
Pro
49 matches
Mail list logo
