Thank you!
Control: tags -1 -moreinfo
Now I named (hopefully) all.
But how shall I name the Free Software Foundation?
Is there an easier way to obtain all used licenses?
Actually I use
`licensecheck --check '.py|js|html|rst|sh' --recursive --deb-machine
--merge-licenses --lines 0 *`
Or can I use just its output?
Control: tags -1 moreinfo
On Mon, 3 Oct 2022 17:36:53 + =?UTF-8?B?QW5kcsOp?=
wrote:
> No. Please check the copyright format description for the "with" keyword.
> Also, please try to present the copyright info in a more consice way.
When two file groups have the same copyright
>
Control: tags -1 -moreinfo
I did not receive the bts email.
> No. Please check the copyright format description for the "with" keyword.
> Also, please try to present the copyright info in a more consice way.
When two file groups have the same copyright
> holders please merge them (combining
Control: tags -1 moreinfo
On Sun, 2 Oct 2022 18:02:38 + wrote:
Control: tags -1 -moreinfo
> d/copyright
> ===
>
> Some GPL-2+ licensed files have the following additional exception:
> # The developers of the Exaile media player hereby grant permission
> # for non-GPL
Control: tags -1 -moreinfo
> d/copyright
> ===
>
> Some GPL-2+ licensed files have the following additional exception:
> # The developers of the Exaile media player hereby grant permission
> # for non-GPL compatible GStreamer and Exaile plugins to be used and
> # distributed together
Control: tags -1 moreinfo
d/copyright
===
Some GPL-2+ licensed files have the following additional exception:
# The developers of the Exaile media player hereby grant permission
# for non-GPL compatible GStreamer and Exaile plugins to be used and
# distributed together with GStreamer
On Thu, 15 Sep 2022 00:27:15 +0200 Bastian Germann wrote:
> On Tue, 13 Sep 2022 17:09:42 + =?UTF-8?B?QW5kcsOp?=
wrote:
> >
> > > No, you have not got it. But maybe this is because of a change in
the
> > GitHub release page:
> > >
> > > $ uscan --download-current-version
> > > uscan
On Tue, 13 Sep 2022 17:09:42 + =?UTF-8?B?QW5kcsOp?=
wrote:
> No, you have not got it. But maybe this is because of a change in the
GitHub release page:
>
> $ uscan --download-current-version
> uscan warn: In debian/watch no matching hrefs for version 4.1.2 in
watch line
>
> No, you have not got it. But maybe this is because of a change in the
GitHub release page:
>
> $ uscan --download-current-version
> uscan warn: In debian/watch no matching hrefs for version 4.1.2 in
watch line
> https://github.com/exaile/exaile/releases .*/?(\d\.\d.\d*)\.tar\.gz
Works if
On Tue, 6 Sep 2022 21:58:08 + =?UTF-8?B?QW5kcsOp?=
wrote:
Control: tags -1 -moreinfo
> You have NOT tested the file with the given command. Please remove
the orig tarball to test it.
> Hint: You are currently requesting a *-*.tar.gz file which worked for
the beta but does not for the
Control: tags -1 -moreinfo
> You have NOT tested the file with the given command. Please remove
the orig tarball to test it.
> Hint: You are currently requesting a *-*.tar.gz file which worked for
the beta but does not for the regular release.
Now I got it. Thanks for the hint.
>
> > One
Control: tags -1 moreinfo
On Mon, 22 Aug 2022 20:48:47 + =?UTF-8?Q?Andr=c3=a9_Flechs?=
wrote:
Control: tags -1 -moreinfo
> Hm... You did not answer where you have got the original from.
> This file seems to be very different from d3.js in
Control: tags -1 -moreinfo
> Hm... You did not answer where you have got the original from.
> This file seems to be very different from d3.js in
https://github.com/d3/d3/releases/download/v3.4.9/d3.zip
I was quite sure to use exactly the file from this source. May be it was
broken after the
Control: tags -1 moreinfo
Your d/watch file does not work. You want to scan GitHub releases and not tags
and fix the version regex.
Also, your orig tarball does not fit the released tar.gz because it has
differences in pt.po.
Please test the download via uscan --download-current-version.
Please remove debian/readme as it does not contain additional info.
There are two problems with d/changelog:
Please use the luzip665 name/email for the signature lines
because exaile is obviously not a natural
person.
The "Beta release" description is not true anymore.
Please just write
On Wed, 3 Aug 2022 23:09:21 + andre-fle...@posteo.de wrote:
Did it by reformating.
Hm... You did not answer where you have got the original from.
This file seems to be very different from d3.js in
https://github.com/d3/d3/releases/download/v3.4.9/d3.zip
Also,
Control: tags -1 -moreinfo
Did it by reformating.
Shall I also handle warnings?
On Fri, 8 Jul 2022 19:19:32 + andre-fle...@posteo.de wrote:
Got it so far.
But there is one lintian error I have no idea about.
Please also fix description-starts-with-package-name.
There is an error about missing source of d3.js. For this I added (I
hope) the source file to missing
Got it so far.
But there is one lintian error I have no idea about.
There is an error about missing source of d3.js. For this I added (I
hope) the source file to missing sources.
But the error does not dissappear. I think it's because of one very long
line 7796.
How can I handle this? Just
As you have closed #672574 and #726559 via BTS already for a different version
please remove them from the changelog.
On Thu, 16 Jun 2022 05:10:41 + andre-fle...@posteo.de wrote:
I had a look at all issues.
That three bugs you mentioned are either fixed (#785897) or
unreproducible
Please build the binary package as well!
Am 30.06.22 um 00:06 schrieb André Flechs:
Running on sid using version 2.115.2 (that seems more recent than that one on
Mentors)
Finally I got one error and one warning. Exactly the same as on Mentors.
Am 29.06.22 um 23:16 schrieb Bastian Germann:
Running on sid using version 2.115.2 (that seems more recent than that
one on Mentors)
Finally I got one error and one warning. Exactly the same as on Mentors.
Am 29.06.22 um 23:16 schrieb Bastian Germann:
Am 29.06.22 um 23:08 schrieb André Flechs:
But why are there differences between
Am 29.06.22 um 23:08 schrieb André Flechs:
But why are there differences between your list and the list of Mentors?
I guess mentors lintian is old.
I did install and just run ;-)
So I will upgrade to sid.
But why are there differences between your list and the list of Mentors?
Am 29.06.22 um 23:05 schrieb Bastian Germann:
Am 29.06.22 um 22:50 schrieb André Flechs:
I tried but it seems complex. How should I run lintian locally?
Install
Am 29.06.22 um 22:50 schrieb André Flechs:
On local Debian 11 with v2.104.0 only two warnings are reported.
You should really develop on sid.
Am 29.06.22 um 22:50 schrieb André Flechs:
I tried but it seems complex. How should I run lintian locally?
Install it and after building your package type "lintian" into your terminal
and press Enter...
debhelper is moved to 12.
I tried but it seems complex. How should I run lintian locally?
In mentors.debian.net the lintian reports only one error: source-is-missing
Your list contains many errors.
On local Debian 11 with v2.104.0 only two warnings are reported.
Thanks in advance,
André
Am
On Mon, 27 Jun 2022 17:16:54 + andre-fle...@posteo.de wrote:
I updated the package and send mails to almost all bugs.
There is only one issue left in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706983. How should I
handle this?
Mentors gives a hint about
"Package uses
Control: tags -1 -moreinfo
Hi Bastian,
I updated the package and send mails to almost all bugs.
There is only one issue left in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706983. How should I
handle this?
Thanks again to David for the explanations.
Kind regards,
André
Control: tags -1 moreinfo
Hi André,
I am tagging moreinfo again. When you have uploaded another version that fixes
the changelog, please untag.
Hi,
On Thu, Jun 16, 2022 at 05:10:41AM +, André Flechs wrote:
> > For the others: Please only add them when you are sure they are resolved.
> > If you are not sure or you do not have the time for them, please leave
> > them untouched.
>
> How should I write the changelog to close
I had a look at all issues.
That three bugs you mentioned are either fixed (#785897) or
unreproducible (#726559, #672574).
Same with the other bugs on
https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no=exaile
How should I write the changelog to close unreproducible or fixed bugs?
On Tue, 7 Jun 2022 16:32:40 + andre-fle...@posteo.de wrote:
I added all issues to changelog as Closes.
Have you really had a look at them? You do not just close them with no comment
in your changelog.
When you have verified the three bugs that I mentioned, please have them in the
line:
Am 07.06.2022 um 18:32 teilte André Flechs mit:
I added all issues to changelog as Closes.
How can I remove the tag?
https://www.debian.org/Bugs/server-control
Hilmar
--
sigfault
OpenPGP_signature
Description: OpenPGP digital signature
I added all issues to changelog as Closes.
How can I remove the tag?
37 matches
Mail list logo
