Warning: unable to close filehandle properly: No space left on device during
global destruction.
On Sat, Aug 10, 2019 at 4:51 PM Russ Allbery wrote:
>
> I don't think there was anything specific to
> git-buildpackage there.
Isn't the whole problem specific to git-buildpackage?
> The result is that the patches-applied Debian
> packaging tree is then representable in Git, which did seem
Felix Lechner writes:
> Please forgive me. I misunderstood your original filing.
Oh, it's no problem! Apologies if I came across as upset. I think I
didn't phrase my reply very well.
> Well, I do not use git-buildpackage, and such an intricate and obscure
> solution does nothing for me.
To
Warning: unable to close filehandle properly: No space left on device during
global destruction.
Hi Russ,
On Sat, Aug 10, 2019 at 3:36 PM Russ Allbery wrote:
>
> I would like Lintian to stop complaining about this when a file is
> explicitly added to that directory by the packaging. It's otherwise
> unactionable by the maintainer.
Please forgive me. I misunderstood your original filing.
Felix Lechner writes:
> I don't think this is a bug in Lintian.
> The source tarball xfonts-jmk_3.0.orig.tar.gz contains an empty
> directory 'neep/ascii/':
> $ dget
> http://deb.debian.org/debian/pool/main/x/xfonts-jmk/xfonts-jmk_3.0-22.dsc
> $ tar tf xfonts-jmk_3.0.orig.tar.gz
>
Your message dated Sat, 10 Aug 2019 15:15:28 -0700
with message-id
and subject line Lintian no longer hangs but exits gracefully, and provides a
helpful error message
has caused the Debian Bug report #926799,
regarding lintian: hangs when dpkg-source fails
to be marked as done.
This means that
Processing commands for cont...@bugs.debian.org:
> tags 907727 + moreinfo
Bug #907727 [lintian] source-contains-empty-directory when a patch adds a file
to that directory
Added tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
907727:
Hi Russ,
I don't think this is a bug in Lintian.
The source tarball xfonts-jmk_3.0.orig.tar.gz contains an empty
directory 'neep/ascii/':
$ dget
http://deb.debian.org/debian/pool/main/x/xfonts-jmk/xfonts-jmk_3.0-22.dsc
$ tar tf xfonts-jmk_3.0.orig.tar.gz
. . .
Felix Lechner writes:
> As you already wrote, RST and Markdown are not that different,
> certainly when compared to Docbook. RST, however, is a lot better
> suited for technical documentation, especially APIs. [1]
For what it's worth, we looked at Markdown for Debian Policy and went with
RST
Warning: unable to close filehandle properly: No space left on device during
global destruction.
Hi Chris,
tldr; I am comfortable with any format you like, but please consider
that I have to re-write much of the documentation. Could we convert to
Markdown when I am done?
On Sat, Aug 10, 2019 at 10:17 AM Chris Lamb wrote:
>
> So, whilst this might sound like the usual tedious "my format is
Hi Chris,
On Sat, Aug 10, 2019 at 10:17 AM Chris Lamb wrote:
>
> How would this work? We don't install the lintian binary package on
> lindsay.debian.org so this wouldn't bring in extra dependencies
> automatically.
I slowly figured that out with help from olasd and adsb. Why are we
not
Hi Felix,
> Going forward, lintian.d.o would simply depend on 'lintian', in
> addition to any installation prerequisites for the reporting package.
How would this work? We don't install the lintian binary package on
lindsay.debian.org so this wouldn't bring in extra dependencies
automatically.
Hi Felix,
> Lintian's manual was converted to reStructuredText format. This MR uses
> rst2html to generate the HTML version.
First, thanks for working on this. Really appreciated.
So, whilst this might sound like the usual tedious "my format is
better than your format" argument, the consensus
Hi Felix,
> Could we use usertags (or any other mechanism) to separate tag-related
> bug reports from other functionality issues? I like to work on the
> latter.
So, triaging Lintian's many bug reports is already is a bit of a
mission and indeed a little while ago I even removed some categories
Hi Chris,
On Sat, Aug 10, 2019 at 12:56:21PM +0100, Chris Lamb wrote:
> [Let me know if you would no longer like direct CCs for qa-jenkins-dev@ mails]
not being cc:ed would indeed be nice here.
> Please keep them for now; we have not totally replaced them Salsa jobs
> yet (see #930487 et al.)
Warning: unable to close filehandle properly: No space left on device during
global destruction.
On 2019-08-10 01:36, Felix Lechner wrote:
Hi Drew,
On Tue, Aug 6, 2019 at 4:24 AM Drew Parsons
wrote:
This
error running lintian simply means the orig tarball is not present in
the same directory as the changes file that lintian is run against.
Would you please post your *.changes and
[Let me know if you would no longer like direct CCs for qa-jenkins-dev@ mails]
Hi Holger,
> do you still need/use the lintian related tests on jenkins.d.n or have
> you already replaced them with Salsa / Debian CI?
Please keep them for now; we have not totally replaced them Salsa jobs
yet (see
Processing commands for cont...@bugs.debian.org:
> tags 865847 + patch
Bug #865847 [lintian] lintian: Migrate manual generation away from jw to
something that supports UTF-8 natively
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
865847:
Control: tag -1 + patch
Lintian's manual was converted to reStructuredText format. This MR uses
rst2html to generate the HTML version.
https://salsa.debian.org/lintian/lintian/merge_requests/245
This RST file was generated from the existing manual in Docbook format
using:
pandoc -f
22 matches
Mail list logo
