>>
>> [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 hav
[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
currentl
[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
[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?
[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
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
Hello.
It seems no activtiy in a while. Any progress?
>> 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
> 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
> 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
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
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://
>> [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?
>
> [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
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
> 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 De
> [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
>
> 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’:
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
22 matches
Mail list logo
