On Mon, Jan 09, 2017 at 10:32:06PM +0100, Rohan Garg wrote:
> Hey
>
> > Try your patch on the firefox package in experimental, and the
> > firefox-esr package in testing/unstable.
>
> Gotcha.
>
> Would it be possible meanwhile to fix epoch handling when trying to
> figure out the upstream versio
Hey
> Try your patch on the firefox package in experimental, and the
> firefox-esr package in testing/unstable.
Gotcha.
Would it be possible meanwhile to fix epoch handling when trying to
figure out the upstream version?
Cheers
Rohan Garg
On Mon, Jan 09, 2017 at 09:59:25PM +0100, Rohan Garg wrote:
> Hey
> > This change most likely breaks building ESR and Beta.
> >
>
> Oh, can you give me more info on how I can check my changes against that?
Try your patch on the firefox package in experimental, and the
firefox-esr package in testi
Hey
> This change most likely breaks building ESR and Beta.
>
Oh, can you give me more info on how I can check my changes against that?
> There also needs to be a build dependency on dpkg-dev >= 1.16.1.
>
The package already depends on dpkg-dev >= 1.16.1 according to the build-deps
Cheers
Rohan
On Mon, Jan 09, 2017 at 05:17:16PM +0100, Rohan Garg wrote:
> Source: firefox
> Severity: normal
> Tags: patch
>
> Dear Maintainer,
> The current debian/upstream.mk seems to be figuring out the source
> and version values manually by calling dpkg-parsechangelog. Instead,
> one could include pkg-in
Source: firefox
Severity: normal
Tags: patch
Dear Maintainer,
The current debian/upstream.mk seems to be figuring out the source
and version values manually by calling dpkg-parsechangelog. Instead,
one could include pkg-info.mk and use the variables exported by
that make file in order to avoid the
6 matches
Mail list logo