On 05 Feb 2018, Juhani Numminen wrote:
>I think you will also need to clean up the generated file, e.g. put it
>into debian/clean.
Indeed. All these changes are now pushed as:
https://salsa.debian.org/debian/bash-completion/commit/1bbccc5353cbe2bb85bc9f487a632cace01c8aa9
As usual, the file at
Gabriel F. T. Gomes kirjoitti 04.02.2018 klo 23:05:
> On 03 Feb 2018, Juhani Numminen wrote:
>
>> Instead of doing version parsing the hard way, could you perhaps
>> include /usr/share/dpkg/pkg-info.mk and use a suitable variable that
>> it defines?
>
> Indeed, but you also made me realize that th
On 03 Feb 2018, Juhani Numminen wrote:
>
>Quick note regarding debian/rules (which I only read online).
>https://salsa.debian.org/debian/bash-completion/blob/unstable/debian/rules
>
>debhelper(7) manpage tells me that autoreconf is enabled by default
>since compat 10, which means that "--with autor
Gabriel F. T. Gomes kirjoitti 03.02.2018 klo 01:41:
> I have more updates to this RFS, which:
>
> - Fix most lintian warning (pedantic) [*].
> - Fix a new bug report (just mark it as fixed, really) [1].
> - Update debhelper version to 11.
Quick note regarding debian/rules (which I only read
I have more updates to this RFS, which:
- Fix most lintian warning (pedantic) [*].
- Fix a new bug report (just mark it as fixed, really) [1].
- Update debhelper version to 11.
The new commits are in the repository [2]. The new package is on
mentors [3][4].
I'm still looking for a sponsor
The repository for the packaging of bash-completion is now hosted on
https://salsa.debian.org/debian/bash-completion/
The latest commit is not on the master branch, but on
https://salsa.debian.org/debian/bash-completion/commits/unstable
Mentors has been updated with a new build:
https://mentors
On 02 Jan 2018, Andrew Shadura wrote:
>
>On 2 January 2018 at 02:17, Gabriel F. T. Gomes
> wrote:
>>
>> When I created the repository in my own server, I named the
>> repository bash-completion-debian.git. When I cloned it to
>> salsa.debian.org, under my personal profile, I kept the "-debian"
>>
On 2 January 2018 at 02:17, Gabriel F. T. Gomes
wrote:
> On 31 Dec 2017, Andrew Shadura wrote:
>
>>On 30 December 2017 at 15:08, Gabriel F. T. Gomes
>> wrote:
>>>
>>> 2. Even though I read the discussions about salsa on debian-devel, I
>>> still do not know how to name the repository. When browsi
On 31 Dec 2017, Andrew Shadura wrote:
>On 30 December 2017 at 15:08, Gabriel F. T. Gomes
> wrote:
>>
>> 2. Even though I read the discussions about salsa on debian-devel, I
>> still do not know how to name the repository. When browsing the
>> projects under the Debian group, I got the impression
On 30 Dec 2017, Ben Finney wrote:
>"Gabriel F. T. Gomes" writes:
>
>> Not really. If I understood it correctly, anonscm.debian.org is
>> alioth, which was being decomissioned when I started to work on
>> this.
>
>The name ‘anonscm.debian.org’ was explicitly det up so that it could
>survive cha
On Fri, Dec 29, 2017 at 08:09:07PM -0200, Gabriel F. T. Gomes wrote:
On 29 Dec 2017, Vincent Blut wrote:
With this release, you can close #847971 too. ;-)
Oh, great! :)
I added this information to the changelog so that the bug gets closed
automatically (I also resubmitted to mentors).
Awe
On Friday, December 29 2017, Gabriel F. T. Gomes wrote:
> On 29 Dec 2017, Sergio Durigan Junior wrote:
>>On Friday, December 29 2017, Gabriel F. T. Gomes wrote:
>>> On 22 Dec 2017, Sergio Durigan Junior wrote:
>>>
>>Yeah, that's right. I'm still using git.debian.org for my packages,
>>but I shoul
On 29 Dec 2017, Vincent Blut wrote:
>With this release, you can close #847971 too. ;-)
Oh, great! :)
I added this information to the changelog so that the bug gets closed
automatically (I also resubmitted to mentors).
Thanks.
pgpvgCnbJ0Prk.pgp
Description: OpenPGP digital signature
"Gabriel F. T. Gomes" writes:
> Not really. If I understood it correctly, anonscm.debian.org is
> alioth, which was being decomissioned when I started to work on this.
The name ‘anonscm.debian.org’ was explicitly det up so that it could
survive changes to a different host, by serving whatever i
Hi Gabriel,
On Fri, Dec 29, 2017 at 05:56:36PM -0200, Gabriel F. T. Gomes wrote:
On 29 Dec 2017, Sergio Durigan Junior wrote:
On Friday, December 29 2017, Gabriel F. T. Gomes wrote:
On 22 Dec 2017, Sergio Durigan Junior wrote:
Yeah, that's right. I'm still using git.debian.org for my packa
On 29 Dec 2017, Sergio Durigan Junior wrote:
>On Friday, December 29 2017, Gabriel F. T. Gomes wrote:
>> On 22 Dec 2017, Sergio Durigan Junior wrote:
>>
>Yeah, that's right. I'm still using git.debian.org for my packages,
>but I should change that as well.
I changed to the new server and fixed th
On Friday, December 29 2017, Gabriel F. T. Gomes wrote:
> On 22 Dec 2017, Sergio Durigan Junior wrote:
>
>>As promised, here's my review.
>
> Thank you! ^^
>
>>The first thing I did was to "gbp
>>clone" your repository and build it locally. After that, I ran:
>>
>> lintian -EI --pedantic bash-co
On 22 Dec 2017, Sergio Durigan Junior wrote:
>As promised, here's my review.
Thank you! ^^
>The first thing I did was to "gbp
>clone" your repository and build it locally. After that, I ran:
>
> lintian -EI --pedantic bash-completion_2.7-1_amd64.changes
>
>And noticed a few things worth fixing
On Sunday, October 01 2017, Gabriel F. T. Gomes wrote:
> Package: sponsorship-requests
> Severity: normal
>
> Dear mentors,
>
> I am looking for a sponsor for my package "bash-completion"
>
> * Package name: bash-completion
>Version : 1:2.7-1
>Upstream Author : Bash Completion
Hi, Andreas,
Does this new version correctly addresses your concerns about the
missing NMUs? (And are there any other NMUs which I might have failed
to find?)
Thank you,
Gabriel
On 23 Oct 2017, Gabriel F. T. Gomes wrote:
>On 10 Oct 2017, Andreas Henriksson wrote:
>
>>You seem to have missed to
On 10 Oct 2017, Andreas Henriksson wrote:
>You seem to have missed to incorporate all the NMUs of
>bash-completion... (atleast they where not part of the
>debian/changelog) Is there any reason why you did not include those
>changes? Won't your updated version conflict with packages who now
>ships
On Tue, 10 Oct 2017, Andreas Henriksson wrote:
>You seem to have missed to incorporate all the NMUs of
>bash-completion... (atleast they where not part of the
>debian/changelog) Is there any reason why you did not include those
>changes?
No reason, other than sheer inexperience. :)
I'll look int
Hello Gabriel F. T. Gomes,
On Sun, Oct 01, 2017 at 07:40:40PM -0300, Gabriel F. T. Gomes wrote:
[...]
> I am looking for a sponsor for my package "bash-completion"
[...]
> Alternatively, one can download the package with dget using this command:
>
> dget -x
> https://mentors.debian.net/debian/
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "bash-completion"
* Package name: bash-completion
Version : 1:2.7-1
Upstream Author : Bash Completion Maintainers
* URL : https://github.com/scop/bash-completion
24 matches
Mail list logo
