[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#930709: marked as done (RFS: pveclib/1.0.1-1 [ITP])



Your message dated Sat, 22 Jun 2019 19:48:06 +0200
with message-id <20190622174806.GA29223@angband.pl>
and subject line Re: Bug#930709: RFS: pveclib/1.0.1-1 [ITP]
has caused the Debian Bug report #930709,
regarding RFS: pveclib/1.0.1-1 [ITP]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
930709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930709
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist

Hi, mentors,

I have filled the RFS template below, but I have a few words beforehand.

1. I know we are under the freeze, so I was a bit wary to send the RFS
now.  On the other hand, I didn't actually find anything saying that I
should wait for the freeze to lift, so I decided to send it.  Correct me
if I am wrong, please.

2. I have worked with upstream to get my concerns fixed (as you may see
in the ITP thread at https://bugs.debian.org/929405).  Upstream was
really helpful and responsive, so if other problems come up, I'm
confident that they can be solved upstream first.

3. This is the second package I make from scratch.  The first was pragha.
Besides that, I maintain bash-completion, which I adopted about a year
ago.  However, the email address in them (gabriel@inconstante.eti.br)
is a bit different from this one (and a lot of people have trouble
writing it down, so I'm unhappy with it)...  Both addresses are listed
as uid in my gpg key, and I would like to use this new address from now
on (with plans to update the address in the other packages).  If that
is a problem, I can switch back to the old one (I suppose it isn't,
because DMs should have a way to switch to @debian.org addresses once
they become DDs, but I digress).

4. This is a powerpc package, so you might need access to a powerpc
server in order to test it.  If you haven't got one at home, :B, you
can get access to a VM at http://openpower.ic.unicamp.br/minicloud/
(that's what I used).

Now, the regular RFS stuff... :)

I am looking for a sponsor for my package "pveclib"

 * Package name    : pveclib
   Version         : 1.0.1-1
   Upstream Author : Steven Munroe <munroesj52@gmail.com>
 * URL             : https://github.com/open-power-sdk/pveclib
 * License         : Apache License 2.0
   Section         : libs

It builds those binary packages:

 * libpvec-dev - Development files for the Power Vector Library
 * libpvec0 - Power Vector Library

To access further information about this package, please visit the following URL:

  https://mentors.debian.net/package/pveclib

Alternatively, one can download the package with dget using this command:

  dget -x https://mentors.debian.net/debian/pool/main/p/pveclib/pveclib_1.0.1-1.dsc

Changes since the last upload:

  This is the first upload to mentors


Kind regards,
Gabriel

--- End Message ---
--- Begin Message ---
On Tue, Jun 18, 2019 at 10:21:05PM -0300, Gabriel F. T. Gomes wrote:
> 1. I know we are under the freeze, so I was a bit wary to send the RFS
> now.  On the other hand, I didn't actually find anything saying that I
> should wait for the freeze to lift, so I decided to send it.  Correct me
> if I am wrong, please.

The freeze affects only packages that have a version in Buster.  And even
for those, there's experimental that's always open.

Your package is NEW, thus it's perfectly fine to upload it at any time.

> 3. This is the second package I make from scratch.  The first was pragha.
> Besides that, I maintain bash-completion, which I adopted about a year
> ago.  However, the email address in them (gabriel@inconstante.eti.br)
> is a bit different from this one (and a lot of people have trouble
> writing it down, so I'm unhappy with it)...  Both addresses are listed
> as uid in my gpg key, and I would like to use this new address from now
> on (with plans to update the address in the other packages).  If that
> is a problem, I can switch back to the old one (I suppose it isn't,
> because DMs should have a way to switch to @debian.org addresses once
> they become DDs, but I digress).

The email address doesn't matter, only the key used does.  If you have key
DEADBEEF that's allowed to upload package chopped-cow, you may upload that
no matter what name is in the control file or changelog.

Heck, just seconds ago, the package got uploaded with:
    Maintainer: Gabriel F. T. Gomes <gabriel@inconstante.net.br>
    keyid: FD9CE2D8D7754B78AB279BBD2C3B436FEAC68101
and I'm pretty sure that key EAC68101 is not yours.

> 4. This is a powerpc package

ppc64el only, actually.  The difference matters -- even if folks use that
name in casual talk, too many people and machines will assume that "powerpc"
means big-endian 32-bit ancient-ISA ancient-ABI.

> so you might need access to a powerpc
> server in order to test it.  If you haven't got one at home, :B, you
> can get access to a VM at http://openpower.ic.unicamp.br/minicloud/
> (that's what I used).

It fails tests in qemu-user, works fine on Debian-provided porterbox.

>  * Package name    : pveclib
>    Version         : 1.0.1-1
>    Upstream Author : Steven Munroe <munroesj52@gmail.com>
>  * URL             : https://github.com/open-power-sdk/pveclib

>  * libpvec-dev - Development files for the Power Vector Library
>  * libpvec0 - Power Vector Library

All looks fine.  I did not test the functionality (beyond the testsuite),
but packaging looks good.

Uploaded, thanks for your contribution!


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Sometimes you benefit from delegating stuff.  For example,
⢿⡄⠘⠷⠚⠋⠀ this way I get to be a vegetarian.
⠈⠳⣄⠀⠀⠀⠀

--- End Message ---

Reply to: