Am Sonntag, den 06.10.2019, 22:09 +0200 schrieb Bernd Zeimetz:
> Hi,
>
> > I'm struggling with it for a while now and I couldn't find the solution.
> > I have a package maintained with git-buildpackage. And now, that I
> > "cannot" upload binary packages I tried to compile the new version with
> >
Am Sonntag, den 06.10.2019, 11:27 +0200 schrieb Alf Gaida:
> On 06.10.19 08:18, Attila Szalay wrote:
> > That option means that the system will create not only the binary
> > .amd.changes but another changes too which contains only the source
> > packages. And I would like to use this method to be
On 10/6/19 11:15 PM, PICCA Frederic-Emmanuel wrote:
> And what about
>
> dgit --gbp push-source ?
not going to touch that. dgit is imho way to over-engineered while
having requirements at the same time, that I don't want to have (like
using dgit.debian.org...).
We have salsa as central reposit
Hi,
> I'm struggling with it for a while now and I couldn't find the solution.
> I have a package maintained with git-buildpackage. And now, that I
> "cannot" upload binary packages I tried to compile the new version with
> the option to create a source-only changes file too. But for some reason
>
On Sun, Oct 6, 2019 at 6:27 PM Alf Gaida wrote:
>
> On 06.10.19 08:18, Attila Szalay wrote:
> > That option means that the system will create not only the binary
> > .amd.changes but another changes too which contains only the source
> > packages. And I would like to use this method to be sure the
On 06.10.19 08:18, Attila Szalay wrote:
> That option means that the system will create not only the binary
> .amd.changes but another changes too which contains only the source
> packages. And I would like to use this method to be sure the package
> compiles, to be able to run the lintian agains
That option means that the system will create not only the binary
.amd.changes but another changes too which contains only the source
packages. And I would like to use this method to be sure the package
compiles, to be able to run the lintian against the package and even be
able to test it before t
On 05.10.19 23:14, Andrey Rahmatullin wrote:
> On Sat, Oct 05, 2019 at 10:02:54PM +0200, Alf Gaida wrote:
that is miss something - my point is: Why do you invoke pbuilder (read
the same question about sbuild too) to create pure source packages?
>>> To make sure they build correctly.
>>>
On Sat, Oct 05, 2019 at 10:02:54PM +0200, Alf Gaida wrote:
> >> that is miss something - my point is: Why do you invoke pbuilder (read
> >> the same question about sbuild too) to create pure source packages?
> > To make sure they build correctly.
> >
> Ok, checked the calender, it is not April 1. I
On 05.10.19 21:48, Andrey Rahmatullin wrote:
> On Sat, Oct 05, 2019 at 08:06:56PM +0200, Alf Gaida wrote:
>> that is miss something - my point is: Why do you invoke pbuilder (read
>> the same question about sbuild too) to create pure source packages?
> To make sure they build correctly.
>
Ok, che
On Sat, Oct 05, 2019 at 08:06:56PM +0200, Alf Gaida wrote:
> that is miss something - my point is: Why do you invoke pbuilder (read
> the same question about sbuild too) to create pure source packages?
To make sure they build correctly.
--
WBR, wRAR
signature.asc
Description: PGP signature
On 05.10.19 19:48, Attila Szalay wrote:
> Hi,
>
> I'm struggling with it for a while now and I couldn't find the
> solution. I have a package maintained with git-buildpackage. And now,
> that I "cannot" upload binary packages I tried to compile the new
> version with the option to create a source
12 matches
Mail list logo
