Mentors,
I am picking up work on this package. I'm working through the issues
already outlined to make sure they are resolved and all questions are
answered.
Once that is done, I'll refresh the package if necessary, and inform of
the updates and answered questions.
Thanks.
Barry Arndt
IBM
Hi,
We've made a new upload. Please, consider this .dsc ->
https://mentors.debian.net/debian/pool/main/c/cxlflash/cxlflash_4.3.2560-1.dsc
Thanks,
Rodrigo R. Galvao
Hi,
The latest version of this package fix the issues pointed in the
previous comment, as well as other points made in mentors.debian.
Here is the link to the .dsc ->
https://mentors.debian.net/debian/pool/main/c/cxlflash/cxlflash_4.3.2554-1.dsc
Thanks,
Rodrigo R. Galvao
Control: tags -1 - moreinfo
src/build/install/resources/{cap,ptd}.gz are prebuilt binaries too.
If you remove them too, and are sure there is no other such things, you
may change the package bacn to main from non-free.
cxlffdc won't work on Debian properly, I suspect there are other things
like
On Mon, Aug 28, 2017 at 06:50:49PM +, Michael P Vageline wrote:
> The firmware and prebuilt binaries are covered under the
>click-to-accept license.
So it's not permitted for Debian to distribute them?
--
WBR, wRAR
signature.asc
Description: PGP signature
On Mon, Aug 28, 2017 at 05:03:02PM +, Michael P Vageline wrote:
> 1. cxlflash depends upon libudev1 and libcxl1 for their runtime shared
> libraries
${shlibs:Depends} already covers that and does the job better.
> 2. The include files were modified, so no copyright update appears to be
>
Hi,
This upload has the changes pointed by Michael in the previous message
->
https://mentors.debian.net/debian/pool/non-free/c/cxlflash/cxlflash_4.3.2533-1.dsc
Thanks,
Rodrigo R. Galvao
..@bugs.debian.org, Michael P Vageline <mpvag...@us.ibm.com>
Subject: Re: Bug#870909: RFS: cxlflash/4.3.2493-1 [ITP] -- IBM Data Engine for
NoSQL Software Libraries
Why does cxlflash explicitly depend on libudev1, libcxl1?
debian/copyright is still not updated.
Why do the maintainer script
Why does cxlflash explicitly depend on libudev1, libcxl1?
debian/copyright is still not updated.
Why do the maintainer scripts use deb-systemd-helper directly and how does
that work with code aded by dh_systemd_*?
I think the licenses shouldn't be in /usr/share/doc but in
/usr/share/pkgname as
Hi Andrey,
> > There are a lot of errors in the install_root_man1 target.
> > There are warnings about unused ${perl:Depends}.
>
>
> We've made changes that should fix these errors. Could you check it,
> please? ->
>
Hi Andrey,
> There are a lot of errors in the install_root_man1 target.
> There are warnings about unused ${perl:Depends}.
We've made changes that should fix these errors. Could you check it,
please? ->
https://mentors.debian.net/debian/pool/non-free/c/cxlflash/cxlflash_4.3.2528-1.dsc
On Thu, Aug 24, 2017 at 10:19:29AM -0300, Rodrigo wrote:
> >> I was able to build from the link I sent to you using 'debuild -us -uc'.
> >> Could you share with us what's the error, please?
> > cflash_block_kern_mc.c:59:10: fatal error: scsi/cxlflash_ioctl.h: No such
> file or directory
>
> We
Hi Andrey,
>> I was able to build from the link I sent to you using 'debuild -us -uc'.
>> Could you share with us what's the error, please?
> cflash_block_kern_mc.c:59:10: fatal error: scsi/cxlflash_ioctl.h: No
such file or directory
We made some changes that fix this build problem. Here is
On Wed, Aug 23, 2017 at 07:23:33PM +, Michael P Vageline wrote:
> Your build error is from missing this file:
> > dpkg -S /usr/include/scsi/cxlflash_ioctl.h
> linux-libc-dev: /usr/include/scsi/cxlflash_ioctl.h
>
> Are you building using a kernel that is shipped with 17.10?
17.10 of what? Your
hi,
Your build error is from missing this file:
> dpkg -S /usr/include/scsi/cxlflash_ioctl.h
linux-libc-dev: /usr/include/scsi/cxlflash_ioctl.h
Are you building using a kernel that is shipped with 17.10?
> Why do both packages depend on some -dev packages?
> *fixed
Why does cxlflash depend
On Wed, Aug 23, 2017 at 03:56:59PM -0300, Rodrigo wrote:
> I was able to build from the link I sent to you using 'debuild -us -uc'.
> Could you share with us what's the error, please?
cflash_block_kern_mc.c:59:10: fatal error: scsi/cxlflash_ioctl.h: No such file
or directory
Besides, you should
Hi,
> I don't really see any changes and also you haven't answered many of
my questions.
> Also, the package doesn't build. Please don't upload packages you haven't
> tested.
I was able to build from the link I sent to you using 'debuild -us -uc'.
Could you share with us what's the error,
On Wed, Aug 23, 2017 at 06:36:21PM +, Michael P Vageline wrote:
> Why do both packages depend on some -dev packages?
> *fixed
Why does cxlflash depend on some -dev packages then?
--
WBR, wRAR
signature.asc
Description: PGP signature
hi,
These are all fixed in the latest... once you get the correct updates.
I: cxlflash: package-contains-empty-directory usr/share/man/man3/
*fixed
I: cxlflash: unused-override hardening-no-fortify-functions
*fixed
/usr/share/cxlflash/readme.txt and maybe some other files should be
hi,
>Do I understand correctly that postinst touches /opt? Including /opt/bin?
>I'm not sure that's a good idea even if that's only for migration (and
>it's definitely a bad idea if anything in /opt is created on a clean
>system).
>As the maintainer script logic is very
On Wed, Aug 23, 2017 at 02:54:18PM -0300, Rodrigo wrote:
> We've made some changes and uploaded it again, here is the link ->
> https://mentors.debian.net/debian/pool/main/c/cxlflash/cxlflash_4.3.2520-1.dsc
I don't really see any changes and also you haven't answered many of my
questions.
Also,
Hi Andrey,
We've made some changes and uploaded it again, here is the link ->
https://mentors.debian.net/debian/pool/main/c/cxlflash/cxlflash_4.3.2520-1.dsc
About the "non-free", how does it work? I mean, we have to change some
file in specific? (i.e. debian/control)
Thanks,
Rodrigo R.
On Wed, Aug 23, 2017 at 05:25:14PM +, Michael P Vageline wrote:
> > *the software for the firmware images will not be included
> Do you mean the images themselves won't be included?
>
> *the binary images are in the cxlflashimage package,
>but the source code won't be included.
hi,
> *the software for the firmware images will not be included
Do you mean the images themselves won't be included?
*the binary images are in the cxlflashimage package,
but the source code won't be included.
Regards,
Mike Vageline
IBM POWER Software Development
On Wed, Aug 23, 2017 at 03:46:35PM +, Michael P Vageline wrote:
> *the software for the firmware images will not be included
Do you mean the images themselves won't be included?
> *we need to allow the click-to-accept license. It is a typical generic
> usage agreement. No fee.
>Our
hi,
> >What are the binaries in src/build/install/resources/ext.tgz? Do they
> > have
> >sources?
> > *they are some specially built utilities with no source.
> Non-free then.
> I also wonder how does that work with both ppc64 and ppc64el
> architectures.
>
> *this is a current
On Wed, Aug 23, 2017 at 02:24:37PM +, Michael P Vageline wrote:
> >Do I understand correctly that postinst touches /opt? Including /opt/bin?
> >I'm not sure that's a good idea even if that's only for migration (and
> >it's definitely a bad idea if anything in /opt is created on a
On Tue, Aug 22, 2017 at 10:16:00PM +, Michael P Vageline wrote:
>hi,
> Thx for your prompt reviews. Here are some more answers:
Please don't send HTML emails.
>Do I understand correctly that postinst touches /opt? Including /opt/bin?
>I'm not sure that's a good idea even if
The package ships firmware, does it have sources? If no, the package must
be in non-free.
What are the binaries in src/build/install/resources/ext.tgz? Do they have
sources?
I: cxlflash: package-contains-empty-directory usr/share/man/man3/
I: cxlflash: unused-override
On Tue, Aug 22, 2017 at 06:54:25PM +0500, Andrey Rahmatullin wrote:
> unexport LD_PRELOAD may be a bad idea.
Actually, have you tried to build this? fakeroot doesn't work.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Tue, Aug 22, 2017 at 09:46:38AM -0300, Rodrigo wrote:
> > > > Please switch to the debhelper compat level 10.
> > Not fixed.
> The debhelper version is set to (>= 10) on debian/control. Is that what you
> meant?
No, debian/compat sets the compat level.
> > > > Why Vcs-Git but no Vcs-Browser?
>
Hi Andrey,
We've made new changes, here is the link to the .dsc file ->
https://mentors.debian.net/debian/pool/main/c/cxlflash/cxlflash_4.3.2520-1.dsc
> > > Please switch to the debhelper compat level 10.
> Not fixed.
The debhelper version is set to (>= 10) on debian/control. Is that what
On Mon, Aug 21, 2017 at 01:52:04PM -0300, Rodrigo wrote:
> Regarding the shared libs, they are installed together in the cxlflash
> package, so they'll all be sync'd in the build process. Besides, we commit
> to never change a shared library published interface in a way it breaks the
> binary
Hi Andrey,
We changed some things based on the points you made. I uploaded the
package again to mentors.debian, here is the link to the .dsc file ->
https://mentors.debian.net/debian/pool/main/c/cxlflash/cxlflash_4.3.2518-1.dsc
Regarding the shared libs, they are installed together in the
Hi,
Here is the link for the .dsc file in mentors.debian ->
https://mentors.debian.net/debian/pool/main/c/cxlflash/cxlflash_4.3.2493-1.dsc
P.S. sorry for the previous html message, I sent it by mistake.
Thanks,
Rodrigo R. Galvao
Control: tags -1 + moreinfo
Maintainer and Uploaders contain the same mpvag...@us.ibm.com email.
Priority should be optional.
Current Standards-Version is 4.0.1.
Please switch to the debhelper compat level 10.
Why do you explicitly B-D on GCC 5?
Why do you B-D on libudev1 and libcxl1?
Why Vcs-Git
Hi Fred,> I didn't check deep but I can see that the packaging is not following> the latest policy manual (newer-standards-version) : have a look to this> document (> https://www.debian.org/doc/packaging-manuals/upgrading-checklist.txt )> to fix this ;
Hi Fred,
> I didn't check deep but I can see that the packaging is not following
> the latest policy manual (newer-standards-version) : have a look to this
> document (
> https://www.debian.org/doc/packaging-manuals/upgrading-checklist.txt )
> to fix this ;
Hi Rodrigo,
I do not intend to sponsor this package but I'm just willing to help.
Be careful to target "Package: sponsorship-request*s*" : the bug as been
properly re-assigned to "sponsorship-requests", but it didn't reach the
mentors audience as I can tell.
I didn't check deep but I can see
Package: sponsorship-request
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "cxlflash"
* Package name: cxlflash
Version : 4.3.2493-1
Upstream Author : Mike Vageline
* URL : https://github.com/open-power/capiflash
*
40 matches
Mail list logo