Am / On Fri, 5 Feb 2021 23:24:07 +0530
schrieb / wrote Utkarsh Gupta :
> I am not sure what's wrong, really. Maybe try doing a
> --fix-missing and update && upgrade manually from inside
> the chroot?
>
> Anyway, everything builds fine here and the autopkgtest
> is passing (superficially) as well a
Hi Klaumi,
On Sat, Jan 30, 2021 at 11:31 PM Klaumi Klingsporn wrote:
> So I think the package is ready for upload, BUT
> the autopkgtest-self initiated by the build-script fails,
> because it's unable to fetch and install an old and
> outdated version of apt-utils: 2.1.11. The
> autopkgtest-self
Am / On Sat, 30 Jan 2021 19:01:00 +0100
schrieb / wrote Klaumi Klingsporn :
> So I think the package is ready for upload, BUT
> the autopkgtest-self initiated by the build-script fails,
> because it's unable to fetch and install an old and
> outdated version of apt-utils: 2.1.11. The
> autopkgtest
Am / On Sat, 14 Nov 2020 16:36:04 +0100
schrieb / wrote Klaumi Klingsporn :
> Am / On Sat, 14 Nov 2020 19:32:40 +0530
> schrieb / wrote Utkarsh Gupta :
>
> > On Sat, Nov 14, 2020 at 7:18 PM Klaumi Klingsporn
> > wrote:
> > > And again thanks for your help. I made a cheat sheet
> > > for the workf
Am / On Sat, 14 Nov 2020 19:32:40 +0530
schrieb / wrote Utkarsh Gupta :
> On Sat, Nov 14, 2020 at 7:18 PM Klaumi Klingsporn
> wrote:
> > And again thanks for your help. I made a cheat sheet for
> > the workflow and all the tips after all. So hopefully
> > next time it will become easier ;-)
>
> T
Hi Klaumi,
On Sat, Nov 14, 2020 at 7:18 PM Klaumi Klingsporn wrote:
> And again thanks for your help. I made a cheat sheet for
> the workflow and all the tips after all. So hopefully next
> time it will become easier ;-)
That's great! Do you think you can put together this thing in a
markdown st
Am / On Sat, 14 Nov 2020 02:59:16 +0100
schrieb / wrote Daniel Leidert :
> I did some fixing
> and also added some superficial autopkgtest test cases
> using the example net.rb script. You can hve a look at it:
>
> - add the team's git repository to yours:
Thanks for the tip which made me reali
Am Freitag, den 13.11.2020, 23:29 +0100 schrieb Klaumi Klingsporn:
> Am / On Fri, 13 Nov 2020 21:53:17 +0100
> schrieb / wrote Daniel Leidert :
>
> > $lintian_opts = ['-i', '-I', '-E', '--pedantic'];
>
> Thanks!
>
> I created a new merge request for you to get my
> latest changes. Just realized,
Am / On Fri, 13 Nov 2020 21:53:17 +0100
schrieb / wrote Daniel Leidert :
> $lintian_opts = ['-i', '-I', '-E', '--pedantic'];
Thanks!
I created a new merge request for you to get my
latest changes. Just realized, that I have to to that ;-)
Klaumi
-
Klaumi Klingsporn
mail: klaumi...@gmx.de
Am Freitag, den 13.11.2020, 19:01 +0100 schrieb Klaumi Klingsporn:
> Am / On Fri, 13 Nov 2020 16:55:53 +0100
> schrieb / wrote Daniel Leidert :
[..]
> > There are some lintian issues to address (enable the
> > pedantic and extra output).
>
> I don't know how to enable this options while lintian
Am / On Fri, 13 Nov 2020 16:55:53 +0100
schrieb / wrote Daniel Leidert :
> Lines must not be longer than 79 characters. That's why I
> suggest to use
>
> * debian/very_long_file_name:
> - long comment with
> linebreak
> - next comment
o.k., done!
> There are some lintian issues
Am Freitag, den 13.11.2020, 15:39 +0100 schrieb Klaumi Klingsporn:
> Am / On Thu, 12 Nov 2020 01:40:48 +0100
> schrieb / wrote Daniel Leidert :
>
> > You can _definitely_ trim debian/changelog. A few hints:
>
> Thanks for your hints. I tried to clean it up accordingly.
>
> > - I wouldn't use su
Am / On Thu, 12 Nov 2020 01:40:48 +0100
schrieb / wrote Daniel Leidert :
> You can _definitely_ trim debian/changelog. A few hints:
Thanks for your hints. I tried to clean it up accordingly.
> - I wouldn't use sublists. Personally I prefer a
> different approach (
> https://salsa.debian.org/rub
Am Mittwoch, den 11.11.2020, 03:16 +0100 schrieb Daniel Leidert:
> Am Mittwoch, den 11.11.2020, 00:42 +0100 schrieb Klaumi Klingsporn:
> > Am / On Tue, 10 Nov 2020 16:53:45 +0100
> > schrieb / wrote Daniel Leidert :
>
> [..]
> > The package builds now and the tests ran without errors :-)
> > Only
Am / On Wed, 11 Nov 2020 14:34:41 +0100
schrieb / wrote Daniel Leidert :
> Nope. You didn't fork the project first. Merge requests
> can only be created for projects with a
> forking-relationship.
So I learned the difference between importing and forking a
project ;-)
> Two options:
>
> 1) Cre
Am Mittwoch, den 11.11.2020, 14:00 +0100 schrieb Klaumi Klingsporn:
> Am / On Wed, 11 Nov 2020 03:16:14 +0100
> schrieb / wrote Daniel Leidert :
>
> > I'll have a look. But you can still create the merge
> > requests. It makes it easier to compare the changes.
> > Because you updated to a newer up
Am / On Wed, 11 Nov 2020 03:16:14 +0100
schrieb / wrote Daniel Leidert :
> I'll have a look. But you can still create the merge
> requests. It makes it easier to compare the changes.
> Because you updated to a newer upstream versuon you must
> create merge requests for all affacted branches inlcud
Am Mittwoch, den 11.11.2020, 00:42 +0100 schrieb Klaumi Klingsporn:
> Am / On Tue, 10 Nov 2020 16:53:45 +0100
> schrieb / wrote Daniel Leidert :
[..]
> The package builds now and the tests ran without errors :-)
> Only a few lintian warnings which I fixed, only the ones
> about missing nmu-entries
Am / On Tue, 10 Nov 2020 21:57:41 +0530
schrieb / wrote Pirate Praveen :
> On 2020, നവംബർ 10 9:23:45 PM IST, Daniel Leidert
> wrote:
> >Ok. The github sources don't contain a .gemspec file but
> >the gem does. The .gemspec is created by a rake task in
> >Rakefile.
> >
> >Three options:
> >1) Add
Am / On Tue, 10 Nov 2020 16:53:45 +0100
schrieb / wrote Daniel Leidert :
> Ok. The github sources don't contain a .gemspec file but
> the gem does. The .gemspec is created by a rake task in
> Rakefile.
>
> Three options:
> 1) Add a patch to create the .gemspec file.
> 2) Run the rake task to crea
On 2020, നവംബർ 10 9:23:45 PM IST, Daniel Leidert wrote:
>Ok. The github sources don't contain a .gemspec file but the gem does. The
>.gemspec is created by a rake task in Rakefile.
>
>Three options:
>1) Add a patch to create the .gemspec file.
>2) Run the rake task to create the gemspec file in
Am Dienstag, den 10.11.2020, 16:23 +0100 schrieb Klaumi Klingsporn:
> Am / On Mon, 09 Nov 2020 23:28:01 +0100
> schrieb / wrote Daniel Leidert :
[..]
> "/usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:101:in
> `block in do_check_dependencies': E: dependency resolution
> check requested but no wor
Am / On Mon, 09 Nov 2020 23:28:01 +0100
schrieb / wrote Daniel Leidert :
> The ruby-tests.* file can be removed. Upstream doesn't
> provide any tests anymore. Not sure why. The commit
> message doesn't mention why the tests have been dropped.
"Ok, I removed the ruby-tests.rb again, the package co
Am Montag, den 09.11.2020, 17:29 +0100 schrieb Klaumi Klingsporn:
> Am / On Mon, 09 Nov 2020 00:28:53 +0100
> schrieb / wrote Daniel Leidert :
>
> > They use a different naming scheme for their source
> > tarballs. This one works:
> >
> > version=4
> > https://github.com/gettalong/cmdparse/releas
Am / On Mon, 09 Nov 2020 00:28:53 +0100
schrieb / wrote Daniel Leidert :
> They use a different naming scheme for their source
> tarballs. This one works:
>
> version=4
> https://github.com/gettalong/cmdparse/releases
> .*/REL_(\d+)_(\d+)_(\d+)@ARCHIVE_EXT@
Thanks, that helped a lot, but I had t
25 matches
Mail list logo
