Bug#925125: Fwd: Fwd: RFS: hollywood/1.14-2 [ITA]

2019-03-19 Thread Emmanuel Arias
Package: sponsorship-requests
Severity: normal


Dear mentors,

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

* Package name    : hollywood
Version : 1.14-2
Upstream Author : Dustin Kirkland 
* URL : https://github.com/dustinkirkland/hollywood
* License : Apache-2.0
Section : games

It builds those binary packages:

hollywood - fill your console with Hollywood melodrama technobabble
wallstreet - fill your console with Wall Street-like news and stats

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

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


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

dget -x
https://mentors.debian.net/debian/pool/main/h/hollywood/hollywood_1.14-2.dsc

More information about hollywood can be obtained from
https://github.com/dustinkirkland/hollywood

Changes since the last upload:

* New Maintainer (Closes: #920883):
  - Add myself to Maintainer field on d/control.
* Bump debhelper to debhelper-compat (= 12) from 11 on d/control.
  - Delete compat file
* Bump Standards-Version to 4.3.0 (from 4.2.1) on d/control.
* Add myself to d/copyright for debian/* files.
* Add Vcs-* links
* Delete snap.wallstret and snap.hollywood folder
  that folder are not in the last upstream version


Regards!

-- 
@eamanu
https://eamanu.com








signature.asc
Description: OpenPGP digital signature


Re: gbp buildpackage test build with uncommitted changes

2019-03-19 Thread Tong Sun
On Tue, Mar 19, 2019 at 1:39 PM Andrey Rahmatullin wrote:
>
> On Tue, Mar 19, 2019 at 01:32:46PM -0400, Tong Sun wrote:
> > > Haven't you seen my email with the correct answer?
> >
> > Too short to figure out what you were trying to say.
> I see.
>
> > In my mind the correct answer is the solution on how to use "gbp
> > buildpackage" to build the package *using* any uncommitted files
> I pointed you to --git-export=WC in that email.

Thanks -- `--git-export=WC` is the solution to my problem.

- - - - - - - - - - - - - - -
--git-export=TREEISH

Instead of exporting the current branch head, export the treeish
object TREEISH. The special name INDEX exports the current index
whereas the special name WC exports the current working copy as is.
Note that using WC enables the --git-ignore-branch and
--git-ignore-new options as well since when exporting the working copy
there's no point in enforcing any branch or modification checks.
- - - - - - - - - - - - - - -



Re: gbp buildpackage test build with uncommitted changes

2019-03-19 Thread Andrey Rahmatullin
On Tue, Mar 19, 2019 at 01:32:46PM -0400, Tong Sun wrote:
> > Haven't you seen my email with the correct answer?
> 
> Too short to figure out what you were trying to say.
I see.

> In my mind the correct answer is the solution on how to use "gbp
> buildpackage" to build the package *using* any uncommitted files
I pointed you to --git-export=WC in that email.

> what  `--git-ignore-new` does or does not.
That is important to understand too, as my impression was you only read
the option name and not its description in the manpage.

-- 
WBR, wRAR


signature.asc
Description: PGP signature


Re: gbp buildpackage test build with uncommitted changes

2019-03-19 Thread Tong Sun
On Tue, Mar 19, 2019 at 1:28 PM Andrey Rahmatullin wrote:
>
> On Tue, Mar 19, 2019 at 12:27:15PM -0400, Tong Sun wrote:
> > Yes, I noticed that `--git-ignore-new` will ignore my changes entirely
> It doesn't do that.
> Also, it all is described in the manpage.
>
> > and the build will keep complaining about the same error that I've
> > already fixed.
> Haven't you seen my email with the correct answer?

Too short to figure out what you were trying to say.

In my mind the correct answer is the solution on how to use "gbp
buildpackage" to build the package *using* any uncommitted files, not
what  `--git-ignore-new` does or does not.



Re: gbp buildpackage test build with uncommitted changes

2019-03-19 Thread Andrey Rahmatullin
On Tue, Mar 19, 2019 at 12:27:15PM -0400, Tong Sun wrote:
> Yes, I noticed that `--git-ignore-new` will ignore my changes entirely
It doesn't do that.
Also, it all is described in the manpage.

> and the build will keep complaining about the same error that I've
> already fixed.
Haven't you seen my email with the correct answer?

-- 
WBR, wRAR


signature.asc
Description: PGP signature


Re: gbp buildpackage test build with uncommitted changes

2019-03-19 Thread Andrey Rahmatullin
On Tue, Mar 19, 2019 at 08:25:53AM -0700, Adam Lewenberg wrote:
> The original question was asking how to use "gbp buildpackage" to build the
> package using any uncommitted files. Doesn't --git-ignore-new _ignore_ the
> uncommitted files?
No, gbp already ignores uncommitted files (without --git-export=WC),
--git-ignore-new just allows you to proceed with building.

> One possibility would be to create a test branch, commit your changes to
> this test branch, and then use the --git-debian-branch option to build on
> this test branch. You can then throw away the branch when you are done.
This is completely unnecessary, of course.

-- 
WBR, wRAR


signature.asc
Description: PGP signature


Re: gbp buildpackage test build with uncommitted changes

2019-03-19 Thread Tong Sun
On Tue, Mar 19, 2019 at 11:42 AM Adam Lewenberg wrote:
>
> On 3/19/2019 3:08 AM, Emmanuel Arias wrote:
> > HI,
> >
> >
> >>> Using `--git-ignore-new` will get my changes ignore entirely, and the
> >>> build will keep complaining about the same error.
> >>>
> >>> What's the solution? Thx
> >>>
> > That is weird. Currently I am working with gbp and --git-ignore-new work
> > for me.
>
>
> The original question was asking how to use "gbp buildpackage" to build
> the package using any uncommitted files. Doesn't --git-ignore-new
> _ignore_ the uncommitted files?

Thanks a lot Adam for paraphrasing what I meant.

Yes, I noticed that `--git-ignore-new` will ignore my changes entirely, and the
build will keep complaining about the same error that I've already fixed.

> One possibility would be to create a test branch, commit your changes to
> this test branch, and then use the --git-debian-branch option to build
> on this test branch. You can then throw away the branch when you are done.

Gotya. Thx.



Re: gbp buildpackage test build with uncommitted changes

2019-03-19 Thread Adam Lewenberg




On 3/19/2019 3:08 AM, Emmanuel Arias wrote:

HI,



Using `--git-ignore-new` will get my changes ignore entirely, and the
build will keep complaining about the same error.

What's the solution? Thx


That is weird. Currently I am working with gbp and --git-ignore-new work
for me.



The original question was asking how to use "gbp buildpackage" to build 
the package using any uncommitted files. Doesn't --git-ignore-new 
_ignore_ the uncommitted files?


One possibility would be to create a test branch, commit your changes to 
this test branch, and then use the --git-debian-branch option to build 
on this test branch. You can then throw away the branch when you are done.







Re: gbp buildpackage test build with uncommitted changes

2019-03-19 Thread Andrey Rahmatullin
On Tue, Mar 19, 2019 at 09:01:30AM -0400, Tong Sun wrote:
> On Tue, Mar 19, 2019 at 6:08 AM Emmanuel Arias wrote:
> 
> > >> Using `--git-ignore-new` will get my changes ignore entirely, and the
> > >> build will keep complaining about the same error.
> > >>
> > >> What's the solution? Thx
> > >>
> > That is weird. Currently I am working with gbp and --git-ignore-new work
> > for me.
> 
> Thanks a lot *everyone* for the confirmation!
> 
> Now I need to figure out why it didn't work for me...
What exactly doesn't work now?

-- 
WBR, wRAR


signature.asc
Description: PGP signature


Re: gbp buildpackage test build with uncommitted changes

2019-03-19 Thread eamanu15
> Thanks a lot *everyone* for the confirmation!
>
> Now I need to figure out why it didn't work for me...
>

Are you working on a particular salsa repo?

Could you let's me know what is it? Could you send me the patch
that you want to add?




-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest


Re: gbp buildpackage test build with uncommitted changes

2019-03-19 Thread Tong Sun
On Tue, Mar 19, 2019 at 6:08 AM Emmanuel Arias wrote:

> >> Using `--git-ignore-new` will get my changes ignore entirely, and the
> >> build will keep complaining about the same error.
> >>
> >> What's the solution? Thx
> >>
> That is weird. Currently I am working with gbp and --git-ignore-new work
> for me.

Thanks a lot *everyone* for the confirmation!

Now I need to figure out why it didn't work for me...



Re: gbp buildpackage test build with uncommitted changes

2019-03-19 Thread Emmanuel Arias
HI,


>> Using `--git-ignore-new` will get my changes ignore entirely, and the
>> build will keep complaining about the same error.
>>
>> What's the solution? Thx
>>
That is weird. Currently I am working with gbp and --git-ignore-new work
for me.






signature.asc
Description: OpenPGP digital signature


Re: gbp buildpackage test build with uncommitted changes

2019-03-19 Thread Andrey Rahmatullin
On Mon, Mar 18, 2019 at 11:47:06PM -0400, Tong Sun wrote:
> Using `--git-ignore-new` will get my changes ignore entirely
That's not what --git-ignore-new does. Not using --git-export=WC does
that.

-- 
WBR, wRAR


signature.asc
Description: PGP signature


Re: gbp buildpackage test build with uncommitted changes

2019-03-19 Thread Geert Stappers
On Mon, Mar 18, 2019 at 11:47:06PM -0400, Tong Sun wrote:
> Hi,
> 
> I'm new to Debian packaging and gbp buildpackage, and many time I want
> to try out my fixes without checking them in, would that be possible
> with `gbp buildpackage`?
> 
> Because whenever, I have above situation, gbp buildpackage will complains:
> 
> - - - - - - - - - - - -
> gbp:error: You have uncommitted changes in your source tree:
> gbp:error: On branch master
> Changes not staged for commit:
> . . .
> gbp:error: Use --git-ignore-new to ignore.
> - - - - - - - - - - - -
> 
> Using `--git-ignore-new` will get my changes ignore entirely, and the
> build will keep complaining about the same error.
> 
> What's the solution? Thx
> 

The `--git-ignore-new` works for me.
Currently I have no project at hand to verify   (sorry)

For me is it OK to publish the `gbp clone` URL here.


Groeten
Geert Stappers
-- 
Leven en laten leven