Package: libimage-magick-perl
Version: 8:6.9.11.60+dfsg-1.3+deb11u4
Severity: normal
Ghostscript 9.24 fixed a security problem that this package apparently
carries a patch to work around.
However a vulnerable version of Ghostscript is no longer in the
distribution.
Meanwhile, the workaround brea
At 2024-08-15T13:20:02-0400, Michael Stone wrote:
> > This change was noted in NEWS.
> >
> > I would suggest hooking your config into something that uses the
> > network-online.target target, with a timeout like network-manager
> > and networkd do, so that the boot process doesn't hang. If it's a
> The file readline.pc is provided since bullseye, so imho this bug can
> be closed.
But the history.pc file apparently isn't.
$ dpkg-deb -c libreadline-dev_8.2-1.3_amd64.deb
drwxr-xr-x root/root 0 2023-01-03 14:49 ./
drwxr-xr-x root/root 0 2023-01-03 14:49 ./usr/
drwxr-xr-x root/
Hi Thomas,
At 2023-06-14T17:49:04-0400, Thomas Dickey wrote:
> On Mon, Jun 12, 2023 at 01:56:56AM +, Bjarni Ingi Gislason wrote:
> > Output from "mandoc -T lint lynx.1"
> > mandoc: lynx.1:27:2: WARNING: missing date, using "": TH
> > mandoc: lynx.1:109:2: WARNING: unknown font, skipping reques
Hi Russ,
At 2023-10-15T12:06:14-0700, Russ Allbery wrote:
> Minor point, but since you posted it
No worries!
> "G. Branden Robinson" writes:
>
> > ...
>
> > \- Minus sign or basic Latin hyphen‐minus. \- produces the
> > Uni
At 2023-10-15T10:01:20-0700, Russ Allbery wrote:
> I think my position at this point as pod2man maintainer (not yet
> implemented in podlators) is that every occurrence of - in POD source
> will be translated into \-, rather than using the current heuristics,
> and people who meant to use ‐ should
Hi Wookey,
At 2023-10-15T16:08:32+0100, Wookey wrote:
> OK. So I read all that, and learned a whole load of stuff I was quite
> happy not knowing about.
>
> However despite reading it all, and especially this bit:
> > Whenever I've maintained man pages in roff I tend to be precise in
> > the usag
At 2023-10-14T20:51:27-0600, Antonio Russo wrote:
> I discovered a new pet peeve today: if you search for a command in a
> manual page, say -e in man 1 zgrep, it's a crapshot whether just
> searching for '-e' will find the command or not. The reason is that
> "-" may been accidentally encoded as ‐
At 2023-09-10T21:47:36+0200, Johannes Schauer Marin Rodrigues wrote:
> Quoting Bill Allombert (2023-09-10 18:29:36)
> > On Sun, Sep 10, 2023 at 09:00:22AM -0700, Russ Allbery wrote:
> > > Jonas Smedegaard writes:
> > > >> Hmm, how about providing license-common package and that
> > > >> depends
Package: lintian
Version: 2.116.3
Severity: wishlist
X-Debbugs-Cc: cjwat...@debian.org, sthiba...@debian.org
Background: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785353
Samuel Thibault and Colin Watson have suggested resurrecting this
lintian tag now that groff 1.23.0 handles the underly
X-Debbugs-CC: Bjarni Ingi Gislason
In my opinion, this bug should be reassigned to the zip package.
Also, the correct term is "font translation", not "font transformation".
https://www.gnu.org/software/groff/manual/groff.html.node/Selecting-Fonts.html
At 2023-08-07T22:11:43+, Bjarni Ingi G
At 2023-07-23T09:46:51+0100, Colin Watson wrote:
> On Sat, Jul 22, 2023 at 11:54:24PM -0500, G. Branden Robinson wrote:
> > I know it's not very generous to observe that Sven either made this
> > claim without verifying it first, or had no concern for the facts
> > when m
Hi Colin,
On Sun, 23 Jul 2023 00:37:43 +0100, Colin Watson wrote:
> On Sat, Jul 22, 2023 at 06:46:28PM +0200, Sven Joachim wrote:
> > This version of groff maps an unescaped "-" to HYPHEN rather than
> > HYPHEN-MINUS. Due to that, copying text from manpages or following
> > references in the "SEE
reassign 769626 groff
retitle 769626 groff: want mailcap entries for .ms and .me files
thanks
Since the ms(7) and me(7) macro packages are not shipped in groff-base,
but in groff, these mailcap entries, if ever created, should be provided
in a file /usr/lib/mime/packages/groff in the "groff" packa
Package: dgit
Version: 9.13
Severity: Important
Justification: causes problems for everybody's autopkgtests
I noticed that groff 1.23.0-2 (and -1 before it) will be blocked from
ever migrating to testing due to an autopkgtest failure on EVERY
architecture.
https://tracker.debian.org/pkg/groff
So
itaram
1 Edmond Orignac
1 Eric Allman
4778 G. Branden Robinson
1 George HELFFRICH
33 Ingo Schwarze
1 John Gardner
4 Keith Bostic
25 Keith Marshall
2 Michael J. Karels
1 Nate Bargmann
3 Nikita Ivanov
1 Paul Eggert
71 Peter Schaf
I expect.
Meanwhile I reckon I'll start praying to the gods of backports and point
releases.
Regards,
Branden
[1] https://release.debian.org/testing/freeze_policy.html#soft
[2]
https://git.savannah.gnu.org/cgit/groff.git/tree/ANNOUNCE?id=99e5b4ae55a7c222f6bf57b355289a88d862478d
https://git.sava
I'm attaching a git diff -p of my changes after that, meaning the actual
packaging work.
For the benefit of people reading this message, here are the commit
messages themselves (git log -r HEAD~21..HEAD).
commit 3cff7c6967e89d187efb160ce7d2a09af5ea82aa (HEAD -> master)
Author: G. Branden
At 2023-01-02T18:54:02+0100, Fabio Pedretti wrote:
> upstream bug report was closed with:
> "This code has been rewritten since and almost certainly fixed,
> closing."
Jesus. I'd never trust a claim like that without output from a formal
verification suite to confirm it.
I think we may have a br
package groff
tag 1021961 + upstream
thanks
It seems I can never learn how to get the magic "-1" bug number to work
for me. I suspect it is a curse Anthony Towns laid on me lo these many
years ago...
signature.asc
Description: PGP signature
package groff groff-base
severity 906091 wishlist
reassign 906091 groff-base
retitle groff-base: troff `tm` request has no means of writing non-ASCII
characters
tag 906091 + upstream
thanks
This would be a significant new feature.
See https://savannah.gnu.org/bugs/?63074#comment9 for lengthy ana
At 2022-09-26T15:40:39-0500, G. Branden Robinson wrote:
> > less interprets b^Hbo^Hol^Hld^Hd by outputting the correct escape
> > sequences for the terminal in use.
>
> No, it doesn't, and cannot, because that representation form is
> ambiguous when the character to be o
Hi Mike,
At 2022-07-31T11:54:13-0400, Mike Bianchi wrote:
> I come into this very late and without having studied the on-going
> discussion. For this I apologize.
>
> > However, since many manual pages in existence are incorrect, and
> > they use '-' >>> when they should use '\-' <<< ...
>
> L
I need to amend my recommendations slightly.
pkg-config _will_ need to remain in Build-Depends due to a very recent
change in groff upstream.
> 2022-05-26 G. Branden Robinson
>
> * bootstrap.conf: Add "pkg-config" to `buildreq`. Not having it
> causes
At 2022-05-26T13:13:44+0100, Colin Watson wrote:
> On Wed, May 25, 2022 at 07:55:10PM -0500, G. Branden Robinson wrote:
> > I apologize for filing this bug report a bit prematurely, but I've
> > been working on building groff in a bullseye chroot lately to
> > prepare f
Package: groff
Version: 1.23.0-1
Severity: wishlist
I apologize for filing this bug report a bit prematurely, but I've been
working on building groff in a bullseye chroot lately to prepare for
groff 1.23.0.rc2, and I wanted to document some findings while they were
fresh in my mind.
Here is the c
package groff groff-base
forwarded 192144 https://savannah.gnu.org/bugs/?62298
thanks
I've opened a ticket for this upstream. In reproducing it, I found
diagnostics that no one ever commented on before which suggest that eqn
could be improved, even if it doesn't ultimately make the input
useful i
package groff groff-base
retitle 541688 groff-base: want Unicode box drawing characters in groff_char(7)
tag 541688 + patch upstream
forwarded 541688 https://savannah.gnu.org/bugs/?62296
thanks
I recommend closing this 12 year-old bug.
1. If it wants to add groff special character identifiers of
package groff
forcemerge 982302 952922
thanks
Hi Marc,
Your bug report #952922 appears to have been resolved by the closure of
bug #982302.
Regards,
Branden
signature.asc
Description: PGP signature
I reiterate (after ~17 months) that the suggestion in this bug report is
ill-advised.
ISO 8859-15 (Latin-9) simple _has_ no code point for the acute accent,
any more than ASCII does.
Further, as Jakub Wilk pointed out, it's just plain wrong semantics to
use the \' escape sequence to obtain any fo
Hi Colin,
As you noted in 2009, this is no longer a problem with the Debian
package.
$ dpkg -L groff | grep /img | xargs test -f && echo | cksum \
| awk '/$2 == 0/ {print "$3 is empty"}'
This produces no errors apart from complains from cksum about operating
on a couple of directories.
> You
tag 55 + upstream fixed-upstream
thanks
This bug was found and corrected independently. The fix is expected in
the groff 1.23 release.
commit 2bd31bb3f2de8e8ff21540ca7c247025903d8acc
Author: G. Branden Robinson
Date: Thu Feb 13 20:25:08 2020 +1100
groff(7): Fix style and correctness
d4.
I'm attaching it for extra reassurance.
Regards,
Branden
commit bcdf2f4c7c28328c711c6a7ac2ea17f2ecd5cdd4
Author: G. Branden Robinson
Date: Wed Oct 21 00:29:24 2020 +1100
src/roff/troff/env.cpp: Avoid infinite loop.
* src/roff/troff/env.cpp (environment::possibly_break_line
tag 991633 + upstream fixed-upstream
thanks
As наб noted, this was fixed in upstream commit 21d307286.
https://git.savannah.gnu.org/cgit/groff.git/commit/?id=21d307286a3f82ba9ddf91fa3fc0a2932a4d7c4c
The fix is expected in the groff 1.23.0 release.
Regards,
Branden
signature.asc
Description: P
Hi, Helge!
At 2022-03-14T12:29:26+0100, Helge Kreutzmann wrote:
> Just to ensure that credit is where credit is due: This was a bug
> report by a l10n/i18n team member of Debian and the fix was developed
> by Colin Watson, see:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692765
>
> Thanks
package groff
tag 243238 + upstream fixed-upstream
thanks
Fix expected in groff 1.23.0.
commit 964ea49e4ac5908811f1c434c7d752d1eb2f4179
Author: G. Branden Robinson
Date: Tue Mar 8 01:44:51 2022 +1100
[fonts]: Fix \[oq] and \[cq] in X11 text fonts.
* /font/devX100-12/CB
Fixed upstream and expected in the groff 1.23.0 release.
commit 1b97881fc0e2246cf29b4758139a665c7816ba23
Author: G. Branden Robinson
Date: Sun Sep 12 05:53:43 2021 +1000
[libbib]: Validate input to avoid heap overread.
Since June 1991 if not earlier, groff (technically, the refer
tag -1 + upstream fixed-upstream
thanks
A fix for this problem has been committed upstream and it is expected in
the groff 1.23.0 release.
commit 6692653f7cae4116d4e70318f71b3d0808f2261f
Author: G. Branden Robinson
Date: Sat Sep 11 07:02:07 2021 +1000
[troff]: Clamp negative tab stop
retitle 990406 groff: ".ta T -5" causes troff assertion failure
tag 990406 + upstream
thanks
What's going on is much clearer if groff Git HEAD, thanks to its
improved `assert()` implementation.
$ printf '.ta T -5\n\t' | tg
troff: ../src/roff/troff/env.cpp:2620: distance_to_next_tab(): assertion
package groff-base
tag 710178 + fixed-upstream
thanks
This has been fixed in groff's Git repository and is expected in the
1.23.0 release.
signature.asc
Description: PGP signature
At 2020-11-22T16:08:56+0100, Ingo Schwarze wrote:
[worthy backgrounder snipped]
> There are many obvious problems in the design:
>
> 1. The syntax is not really consistent: both coded references
> like "BSD" "4.4" and free text strings are supported.
Yes, I found this particularly startli
At 2019-12-21T14:51:23+0100, Ingo Schwarze wrote:
> Colin Watson wrote on Tue, Dec 17, 2019 at 01:15:30PM +:
> > On Tue, Dec 17, 2019 at 01:14:06PM +, Colin Watson wrote:
> > Side note: I am not the biggest fan of this business of encoding a
> > bunch of other projects' release history in g
4b3f664b0,
c=, env=0x5634b3f5bb70, widthp=widthp@entry=0x0)
at ../../src/libs/libdriver/printer.cpp:181
181 set_char(g, f, env, w, 0);
##(gdb) list
176
177 buf[0] = c;
178 buf[1] = '\0';
179
180 glyph *g = set_char_and_width(buf, env, &w, &f);
181
If this bug report is asking for a latin9 output driver for groff, it's
should be retitle and moved to wishlist severity.
If it's asking for the semantics of \' to change from acute accent, it's
wontfix.
Regards,
Branden
signature.asc
Description: PGP signature
package gross-base
tag 710178 + fixed-upstream
thanks
This has been fixed in groff's Git repository and is expected in the
1.23.0 release.
https://git.savannah.gnu.org/cgit/groff.git/commit/?id=f75e156b621d3743368c58425f357e6cd52372a0
signature.asc
Description: PGP signature
After 15 years, I recommend closing this bug as "wontfix".
The traditional output mode only makes sense for overstriking terminals,
of which there are vanishingly few that aren't paper terminals, which
are themselves a dead breed.
The virtue of "ANSI escapes" is that they're actually standardized
[groff upstream committer here]
I think there is a bit of a culture clash between BSD and the rest of
the world here. In man(7) pages a fairly common, though not universal,
practice is to use the fourth argument to .TH to designate more or less
a package release of a software project. groff itse
Package: jekyll
Version: 3.8.3+dfsg-4
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I'm trying to debug why some Markdown didn't convert to HTML properly on
a jekyll-generated website. So that
Package: chromium
Version: 72.0.3626.96-1~deb9u1
Severity: grave
Justification: renders package unusable
I have been tracking testing for several months.
This looks to me like a missing or insufficiently versioned Replaces
declaration, but I did not dig deeply into this except to check the BTS
to
change your locale if this is incorrect.
>
> Using '"G. Branden Robinson" ' as your from
> address.
> Retrieving report #541147 from Debian bug tracking system...
> No report available: #541147
> No such bug report.
Huh.
And yet...
> $ bts status 541
Package: xterm
Version: 337-1
Severity: normal
Tags: upstream
The man page says *saveLines defaults to 64. But it really defaults to
1024.
Patch attached. It also synchronizes xterm.dat, whatever that is, with
the application defaults file.
-- System Information:
Debian Release: buster/sid
A
At 2018-11-13T10:37:20+0100, Łukasz Stelmach wrote:
> +// Pressing the Shift+Win (left or right, respectively) acts as Menu
> +// while Shift+Win acts as Menu.
I don't understand this comment; it seems tautologous.
Shouldn't it be more like:
// Pressing left or right Win acts as Win, while Shift
At 2018-11-13T17:02:49+, Ian Jackson wrote:
> G. Branden Robinson writes ("Shouldn't shipping broken symlinks be against
> policy?"):
> > Not reopening, but I have some questions for the Policy team.
> ...
> > I could have sworn you were incorrect, but sur
an \
-type l); do if ! test -f "$F"; then file "$F"; dpkg -S "$F"; fi; done
4938
/usr/share/man/man1/rust-gdb.1.gz: broken symbolic link to gdb.1.gz
rust-gdb: /usr/share/man/man1/rust-gdb.1.gz
> X
>
> G. Branden Robinson:
> > Package: rust-gdb
&
Package: rust-gdb
Version: 1.28.0+dfsg1-2
Severity: normal
File: /usr/share/man/man1/rust-gdb.1.gz
$ dpkg -S /usr/share/man/man1/rust-gdb.1.gz
rust-gdb: /usr/share/man/man1/rust-gdb.1.gz
$ file /usr/share/man/man1/rust-gdb.1.gz
/usr/share/man/man1/rust-gdb.1.gz: broken symbolic link to gdb.1.gz
At 2018-11-10T15:07:23-0200, Gabriel F. T. Gomes wrote:
> Hi,
>
> On 10 Nov 2018, G. Branden Robinson wrote:
>
> >Package: bash-completion
> >Version: 1:2.8-2
> >Followup-For: Bug #742466
> >
> >I'm attaching a debdiff of a proposed NMU for this.
Package: lintian
Version: 2.5.111
Severity: normal
File: /usr/share/lintian/collection/java-info
Now running lintian bash-completion_2.8-2.1_amd64.changes ...
Use of uninitialized value $magic in numeric eq (==) at
/usr/share/lintian/collection/java-info line 115.
Use of uninitialized value $magi
load.
+ * Fix extremely annoying and long-standing breakage of completion
+within POSIX command substitution $(). (Closes: #742466)
+
+ -- G. Branden Robinson Sat, 10 Nov 2018
08:27:09 -0500
+
bash-completion (1:2.8-2) unstable; urgency=low
* Fix for held packages completion in dpkg (C
At 2018-11-09T21:38:46+, Colin Watson wrote:
> Control: tag -1 fixed-upstream
>
> On Fri, Nov 09, 2018 at 02:30:42PM -0500, G. Branden Robinson wrote:
> > $ for F in $(man -w tfmtodit hpftodit afmtodit); do lexgrog "$F"; zcat "$F"
> > | sed -n &#x
Package: man-db
Version: 2.8.4-2+b1
Severity: normal
Tags: upstream
$ for F in $(man -w tfmtodit hpftodit afmtodit); do lexgrog "$F"; zcat "$F" |
sed -n '3,4 {/\\-/p}'; done
/usr/share/man/man1/tfmtodit.1.gz: "tfmtodit - create font files for use with
groff - Tdvi"
tfmtodit \- create font files
Package: evince
Version: 3.30.1-1
Followup-For: Bug #908964
This problem is reproducible on the version of evince in testing, and
with the following trivial document:
$ cat > hello.txt
Hello, world!
Make me with "groff -Tpdf hello.txt > hello.pdf".
-- System Information:
Debian Release: buster/
retitle 470995 ITP: devotee -- Debian voting system
owner 470995 !
thanks
I'll take a crack at this. I'm in pretty frequent contact with Manoj
on Facebook, though we're more often arguing about U.S. politics than
anything to do with Debian or software engineering in general.
He'll be well-situat
At 2018-06-28T11:31:30+0200, Michel Dänzer wrote:
>
> Please send this kind of change directly upstream to the
> amd-...@lists.freedesktop.org list for review, split up into one patch
> per logical change.
Well, a lot of these changes aren't "logical", they're stylistic.
> On 2018-06-27 09:07 PM
At 2018-06-02T17:33:38+0200, Guilhem Moulin wrote:
> Control: tag -1 pending
>
> Hi,
>
> On Sun, 20 Aug 2017 at 21:40:44 -0400, G. Branden Robinson wrote:
> > I'm at a loss for what put my terminal into that state in the first
> > place
>
> Just got an
At 2017-11-07T08:10:40-0500, G. Branden Robinson wrote:
> Here's an updated version of the patch, reverting the de-boldfacing of
> action names (and some token names) in resource translations.
Of course, by sending that I guaranteed I'd find a problem with it.
Here's my n
Here's an updated version of the patch, reverting the de-boldfacing of
action names (and some token names) in resource translations.
My additional fixes are described at the end, numbered 21-25.
Please find two attachments:
1. The actual diff.
2. A diff of the nroffed output of the two pages pr
At 2017-11-06T18:51:32-0500, Thomas Dickey wrote:
> > > > 10. Remove boldfacing from portions of code examples; these escapes
> > > > changed the font family back to Times from Courier. If this change
> > > > is unacceptable, I can come up with one that will stay within the
> > > > Cou
At 2017-11-05T15:11:13-0500, Thomas Dickey wrote:
> On Thu, Nov 02, 2017 at 02:20:54AM -0400, G. Branden Robinson wrote:
> > 10. Remove boldfacing from portions of code examples; these escapes
> > changed the font family back to Times from Courier. If this change
> >
Hi Thomas,
At 2017-11-02T04:55:25-0400, Thomas Dickey wrote:
> thanks - someone reported a problem with the same macro in ncurses.
> (I'll have to make a script to check for other instances, since I've
> used bullets in a lot of places - I've a to-do item for that anyway).
Thanks to a bug in grop
At 2017-11-02T04:55:25-0400, Thomas Dickey wrote:
> thanks - someone reported a problem with the same macro in ncurses.
> (I'll have to make a script to check for other instances, since I've
> used bullets in a lot of places - I've a to-do item for that anyway).
Yeah, I've noticed those. When I r
Package: xterm
Version: 327-2 (but I prepared the diff against xterm-330)
Severity: normal
Tags: upstream
Hi Thomas,
Here's a patch for various markup bugs and inconsistencies in the xterm
man page.
01. The local macro definitions for bP and NS were testing the values of
registers which were
Hi Guilhem!
At 2017-08-20T13:18:06+0200, Guilhem Moulin wrote:
> AFAICT this is caused by `stty -icrnl -icanon`. Running `stty icrnl
> icanon` or `stty sane` before caff(1) should do the trick.
I can confirm this. I did not manually and the bug did not then
reproduce.
I'm at a loss for what pu
Hi Guilhem! Thanks for the prompt follow-up.
I've edited a thinko in my original report below, marked with [] brackets.
At 2017-08-18T15:39:31+0200, Guilhem Moulin wrote:
> On Fri, 18 Aug 2017 at 03:27:14 -0400, G. Branden Robinson wrote:
> > The only way to get past the promp
Package: signing-party
Version: 2.5-1
Severity: normal
File: /usr/bin/caff
The only way to get past the prompt into type Ctrl+J (yes, hold down Control
and press J).
##gpg> save
[INFO] Key 0x283681BA6FE7F41D UID 1 Sam Hartman done
[INFO] Key 0x283681BA6FE7F41D UID 2 Sam Hartman done
Mail signat
At 2017-07-27T13:50:53-0700, Sean Whitton wrote:
> Hello Branden,
>
> On Thu, Jun 15, 2017 at 04:35:23PM +0100, Sean Whitton wrote:
> > Please accept my apologies for letting this RFS sit for so long. Thank
> > you for all your work. Looking forward to uploading it soon.
> >
> > Here's a full r
At 2017-07-26T11:51:10+0200, Nicolas George wrote:
> Package: xdm
> Version: 1:1.1.11-3
> Severity: normal
>
> Dear Maintainer,
>
> When somebody tries to log in and fails, xdm writes the given user name in
> the system logs. Unfortunately, typing the password in the login field is a
> common mis
package sponsorship-requests
tag 859778 - moreinfo
thanks
$ dput mentors xtrs_4.9d-1_amd64.changes
Checking signature on .changes
gpg: /home/branden/src/GIT/debian/xtrs_4.9d-1_amd64.changes: Valid signature
from D19E9C7D71266DCE
Checking signature on .dsc
gpg: /home/branden/src/GIT/debian/xtrs_4
e to not end in "etc." and also add information.
+ * debian/control: Bump Standards-Version to 3.9.8.
+
+ -- G. Branden Robinson Mon, 01 May 2017
11:08:00 -0400
+
shunit2 (2.1.6-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru shunit2-2.1.6/debian/contro
Package: gcc
Version: 4:6.3.0-4
Severity: important
$ man gcc
No manual entry for gcc
See 'man 7 undocumented' for help when manual pages are not available.
$ dpkg -S gcc|grep -F man1/gcc. || echo nope
nope
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'test
At 2017-04-22T16:04:25-0700, Sean Whitton wrote:
> > Can you explain your reasoning here?
>
> Currently, almost all Debian packagers/maintainers use one changelog
> entry and version number per upload. So if there are rounds of review
> in an RFS, new changes are folded into the previous changelo
At 2017-04-23T11:45:03+0200, Julien Cristau wrote:
> The wrapper was moved to the xserver-xorg-legacy package, and I'm a bit
> worried removing the configuration file in the x11-common maintainer
> scripts would break that transition.
Ahhh. Did we never get solid support in dpkg for migrating con
At 2017-04-22T15:41:48-0400, G. Branden Robinson wrote:
> > Given this problem I haven't done a full review, but I'd like to make
> > two preliminary suggestions:
> >
> > 1) How about merging the -1, -2 and -3~~unreleased changelog entries
> > into a
At 2017-04-22T07:13:38-0700, Sean Whitton wrote:
> control: tag -1 +moreinfo
>
> Hello Branden,
>
> I can't get 79e8ccf40499ace8cf36210a7ad9fb157209bbe4 to build. Log
> attached.
Urp. This is due to the unavailabilty of gropdf on the build host, it
looks like. I'll investigate.
> Given this
At 2017-04-20T09:39:42+0200, Guillem Jover wrote:
> On Wed, 2017-04-12 at 11:00:20 -0400, G. Branden Robinson wrote:
> > The former. You'll never see a C library interface manpage with
> > double-colons in the name, and C++ programmers never write manpages
> > because
At 2017-04-20T15:58:04-0700, Sean Whitton wrote:
> Please remove the moreinfo tag from the bug when it's ready to be
> uploaded.
Will do!
Regards,
Branden
signature.asc
Description: PGP signature
At 2017-04-20T09:45:13-0700, Sean Whitton wrote:
> Hello Branden,
Hi Sean!
> On Wed, Apr 12, 2017 at 11:09:45PM -0400, G. Branden Robinson wrote:
> > Yeah, I didn't understand that at the time. Subsequently I changed all
> > the 4.9d changelog entries to target experi
Package: apt
Version: 1.4
Severity: wishlist
File: /usr/bin/apt
Use case:
$ apt search shell | less -r
Apt apparently turns off colorized output if standard output is not a
tty. That's great for redirection to files, but not so much for
redirection to "less -r".
Please give apt a switch so tha
At 2017-04-12T22:49:51+0200, Adam Borowski wrote:
> On Wed, Apr 12, 2017 at 12:28:11PM -0400, G. Branden Robinson wrote:
> > I think I got it fixed.
> >
> > The URL of my package is:
> > https://mentors.debian.net/package/xtrs
> >
> > The respect
On Wed, Apr 12, 2017 at 10:20:55AM -0400, G. Branden Robinson wrote:
> > Hrm #1: GMail helpfully categorized your mail as spam.
>
> Not nice, let's try again; if you don't respond in a day I'll send
> from some other place.
It's fixed. I told GMail you&#x
At 2017-04-09T03:57:01+0200, Guillem Jover wrote:
> Hi!
>
> On Sat, 2017-03-25 at 19:27:55 -0400, G. Branden Robinson wrote:
> > On Sat, Mar 25, 2017 at 03:07:32PM +0100, Guillem Jover wrote:
> > > The implementation in dpkg-dev already supports all of this
> > >
At 2017-04-07T00:44:18+0900, Osamu Aoki wrote:
> Hi,
>
> On Thu, Mar 23, 2017 at 04:45:35PM -0400, Branden Robinson wrote:
> > Package: maint-guide
> > Version: 1.2.38
> > Severity: normal
> >
> > Chapter 1 notes that "This document has been updated fo
At 2017-04-07T15:23:19+0200, Adam Borowski wrote:
> On Fri, Apr 07, 2017 at 07:41:51AM -0400, G. Branden Robinson wrote:
> > * Package name: xtrs
> > Version : 4.9d-2
>
> > https://mentors.debian.net/package/xtrs
> > dget -x
> > ht
At 2017-04-09T13:34:44+0200, Andreas Beckmann wrote:
> 1m37.2s INFO: Warning: Package purging left files on system:
> /etc/X11/Xwrapper.config not owned
It appears the old Xwrapper was killed off at some point.
The patch should be trivial enough that I can do it. This would also
serve as a
At 2017-04-07T20:08:05+0200, Graham Inggs wrote:
> On 7 April 2017 at 19:06, G. Branden Robinson
> wrote:
> > All of this hardening stuff, as I understand it, involves mitigation
> > strategies for unsafe memory usage in the C language family in the ELF
> > object file fo
At 2017-04-07T14:10:06+0200, Graham Inggs wrote:
> On 07/04/2017 13:12, G. Branden Robinson wrote:
> > compile_rom is an utility internal to the build. It's not shipped and
> > thus not subject to attacks. I'm considering adding an --ignore-line
> > for it, but I
At 2017-04-07T12:08:58-0400, James McCoy wrote:
> On Fri, Apr 07, 2017 at 07:23:39AM -0400, G. Branden Robinson wrote:
> > However, my xterms are somewhat customized. I'm attaching my
> > .Xresources file.
>
> Perfect! That seems to be the difference. I, and presumably
Package: sponsorship-requests
Severity: normal
Dear mentors,
I seek a sponsor for my package "xtrs".
* Package name: xtrs
Version : 4.9d-2
Upstream Author : Tim Mann
* URL : http://www.tim-mann.org/xtrs.html
* License : 2 different custom permissive licenses
At 2017-04-06T21:56:13-0400, James McCoy wrote:
> On Fri, Apr 07, 2017 at 12:54:19AM +0200, Francesco Poli wrote:
> > On Thu, 6 Apr 2017 15:06:17 -0400 G. Branden Robinson wrote:
> >
> > > At 2017-04-06T13:33:58-0400, James McCoy wrote:
> > > > On Thu, Apr 06,
ed to figure out how to embed this information in the
package itself so the buildd log scanner knows to use this flag itself.
Please advise if you think the attachments don't address the issue.
Regards,
Branden
xtrs_4.9d-2.debian.tar.xz
Description: application/xz
Format: 3.0 (quilt)
Source:
At 2017-04-06T13:33:58-0400, James McCoy wrote:
> On Thu, Apr 06, 2017 at 01:17:55PM -0400, G. Branden Robinson wrote:
> > The below is not a sufficient reproduction receipe for me.
> >
> > I'm running Debian Stretch (testing).
> >
> > Things do not go wron
1 - 100 of 355 matches
Mail list logo
