-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 30 Mar 2017 09:20:32 -0400
Source: xtrs
Binary: xtrs
Architecture: source
Version: 4.9c-4
Distribution: unstable
Urgency: medium
Maintainer: G. Branden Robinson <g.branden.robin...@gmail.com>
Changed-By: G. Branden Ro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 08 Aug 2018 03:21:44 -0400
Source: xtrs
Binary: xtrs
Architecture: source amd64
Version: 4.9d-1
Distribution: unstable
Urgency: medium
Maintainer: G. Branden Robinson
Changed-By: G. Branden Robinson
Description:
xtrs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 15 Aug 2018 11:59:02 -0400
Source: xtrs
Binary: xtrs
Architecture: source amd64
Version: 4.9d-2
Distribution: unstable
Urgency: low
Maintainer: G. Branden Robinson
Changed-By: G. Branden Robinson
Description:
xtrs
At 2019-06-01T09:04:39+0200, Philipp Kern wrote:
> Are we then looking more closely at AMD-based machines given that
> those had less problems around speculative attacks?
To borrow a phrase from Christopher Hitchens, this comment gives a
hostage to fortune.
My team at work closely follows (and
Hi folks,
It's been a while since I've done any packaging. I was baffled when
presented with the following.
dh_clean
cp: cannot stat
'debian/.debhelper/bucket/files/19c12bb2ca19e68724c2854ed0512469518df19b0710cc2011a5ca540810979c':
No such file or directory
dh_clean: error: cp -an
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
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-22T02:11:15-0700, Steve Langasek wrote:
> SPDX defines an xml format only. They lost before they'd even
> started.
>
> debian/copyright is supposed to be human-readable first and foremost.
> XML need not apply.
Very much +1 on everything quoted.
That said, SPDX's license list and
Hi Andrew,
At 2023-10-23T10:41:10+1300, Andrew Ruthven wrote:
> On Sun, 2023-10-22 at 13:18 +0200, Bastian Venthur wrote:
> > fixed the problem. It is strange this option seems to be affected by
> > the keyboard settings in gnome settings, however i changed all
> > options back and forth in the
At 2023-10-14T20:51:27-0600, Antonio Russo wrote:
> I discovered a new pet peeve today:
I must report with some dismay that this thread made LWN.
https://lwn.net/Articles/947941/
Would someone be willing to send me a subscriber-sponsored link to it?
I intend to attempt to address what I expect
At 2023-10-23T11:17:07-0500, G. Branden Robinson wrote:
> Would someone be willing to send me a subscriber-sponsored link to it?
Thanks to the three fleet-fingered folks who supplied me with one. I am
amply equipped to resume my crusade against ignorance and
misinformation...except...
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
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
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
At 2023-10-15T13:11:47-0700, Russ Allbery wrote:
> Sorry for my original message, which was very poorly worded and
> probably incredibly confusing. Let me try to make less of a hash of
> it. I think what I'm proposing is something like:
My reply to this didn't make it to the -devel list even
Hi Jon,
At 2023-10-23T17:24:30-0600, Jonathan Corbet wrote:
> When I wrote the article (last week) it was a lot closer :)
>
> As for why: Debian may have resolved this, for now at least, but this
> is an issue that is sure to crop up in distributions that are not as
> quick to pick up new groff
At 2023-08-23T15:40:06+0100, Adam Sampson wrote:
> "Andrew M.A. Cater" writes:
> > where are we going to get our fortunes from - where's the canonical
> > source now that FreeBSD has gone?
>
> There is Shlomi Fish's version:
> https://github.com/shlomif/fortune-mod/
I've been mulling over
Hi Hugh,
I work on groff upstream.
At 2023-08-15T22:46:30+1000, Hugh McMaster wrote:
> groff-message an.tmac::66: warning: tbl preprocessor
> failed, or it or soelim was not run; table(s) likely not rendered (TE
> macro called with TW register undefined)
>
> It seems TW is not defined in the
Hi Hugh,
At 2023-08-17T07:54:03+1000, Hugh McMaster wrote:
> On Thu, 17 Aug 2023 at 03:39, Colin Watson wrote:
> > On Wed, Aug 16, 2023 at 09:29:45PM +1000, Hugh McMaster wrote:
> > > This all seems promising. Unfortunately, the man page is
> > > hand-crafted, not generated from another source,
At 2023-08-17T01:37:52+0100, Colin Watson wrote:
> On Wed, Aug 16, 2023 at 07:08:18PM -0500, G. Branden Robinson wrote:
> > [6] https://man.cx/grog
> >
> > I was going to link to
> > https://manpages.debian.org/unstable/groff/grof.1.en.html here, but
>
arbage workers.
At 2023-08-18T21:09:11+, Andrew M.A. Cater wrote:
> As the person who raised this on debian-project in November 2022 - see
> the archives for debian-project for November/December 2022
[...]
> There was unfortunately no consensus on removal on debian-project and
At 2023-03-26T13:56:55-0700, Sean Whitton wrote:
> On Sat 04 Mar 2023 at 10:58PM +01, Joerg Jaspert wrote:
> > But git or svn or even sccs and rcs is NOT, in any way, preferred
> > for of modification. Only one way of storage and handling some
> > metadata.
>
> This is Debian's official position,
D~21..HEAD).
commit 3cff7c6967e89d187efb160ce7d2a09af5ea82aa (HEAD -> master)
Author: G. Branden Robinson
Date: Sat Feb 25 22:53:06 2023 -0600
debian/changelog: Add upstream bug closers.
commit 1fd80f4151713e9f1d3cb52a4b749fa643776908
Author: G. Branden Robinson
Date: Sat Feb 25 22:29:
At 2023-02-26T11:52:39+0100, Andrey Rakhmatullin wrote:
> Just import them? Do you have any specific questions or problems with
> this?
[...]
> Again, which advice? You said that it works for you.
Hi Andrey,
I think at least some of my confusion arose from trying to use gbp with
a git-dpm-based
o 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.savannah.gnu.org/cgit/groff.git/tree/NEWS?id=99e5b4ae55a7c2
[I am not subscribed to debian-gcc or c-std-porting]
Hi Florian,
At 2023-04-18T16:07:45+0200, Florian Weimer wrote:
> TL;DR: I want to propose a GCC 14 change which will impact
> distributions, so I'd like to gather some feedback from Debian.
>
> Clang has disabled support for a few historic C
At 2023-07-21T13:43:05+0200, IOhannes m zmölnig (Debian/GNU) wrote:
> On 7/21/23 12:57, G. Branden Robinson wrote:
> > Hi folks,
> >
> > But I see no mechanism for interacting with autopkgtests to force
> > them to re-run due to the remedy of a defect in the test harne
Hi folks,
Regarding:
https://tracker.debian.org/pkg/groff
...progress of groff into testing is blocked because autopkgtests went
bonkers, failing on every architecture. This was due to a change in a
groff diagnostic message not getting scraped away by dgit, which was
using a regex to match the
At 2023-05-19T15:32:40+0100, Colin Watson wrote:
> I occasionally use 32-bit x86 even today (mostly for not very good
> historical reasons, but nevertheless), and I do it by using a 32-bit
> container on a 64-bit x86 machine instead. It's much faster to run,
> and it doesn't depend on installer
At 2023-05-19T15:03:40+0100, Steve McIntyre wrote:
> Luca Boccassi wrote:
> >+1 for stopping publishing installers for i386, it has been mentioned
> >many times but it's always worth repeating: electricity costs to keep
> >running i386 hardware are already way higher than what it costs to
> >buy a
At 2023-05-17T11:30:36+0200, Helmut Grohne wrote:
> This bootstrap aspect got me and I discussed this with a number of
> people and did some research.
I'd like to nominate you for a Russ Allbery Award for the most useful
post to the thread. Your attention to concrete, empirical details,
arising
[follow-ups should probably go to -project, but I'm not setting my
headers to try to force that]
At 2024-01-24T16:57:06+0100, Simon Josefsson wrote:
> One could equally well make the argument that distributors should care
> about the Go/Rust ecosystems, and make whatever changes needed in
> order
Hi Loren,
At 2024-01-30T19:55:07-0800, Loren M. Lang wrote:
> While building a package preparing for a possible upload, I am getting
> a large number of warnings from groff-message due to invalid fonts for
> C and CB in the manpages that are generated from Markdown with pandoc.
> From what I
package libghc-pandoc-dev
tag 1053777 + fixed-upstream
thanks
Hi Jonas!
At 2024-01-31T08:43:18+0100, Jonas Smedegaard wrote:
> Quoting G. Branden Robinson (2024-01-31 05:49:00)
> > Well, the version of pandoc that resolved the issue was 3.1.7,
> > released in August 2023.[1]
At 2023-11-15T14:58:15+, Jeremy Stanley wrote:
> I replied to you there too, but you still never seemed to be able to
> explain... why do you need to put an OpenPGP key on the service
> you're using to upload Python packages (not Debian packages) to
> PyPI, given that PyPI doesn't support
At 2024-03-30T14:38:03+0200, Jonathan Carter wrote:
> On 2024/03/30 11:05, Simon Josefsson wrote:
> > > 1. Move towards allowing, and then favoring, git-tags over source tarballs
> >
> > Some people have suggested this before -- and I have considered
> > adopting that approach myself, but one
Hi Otto,
At 2024-03-30T14:09:46-0700, Otto Kekäläinen wrote:
> While reviewing xz-utils commits I noticed that a bunch of old
> copyright holder names were removed in
> https://salsa.debian.org/debian/xz-utils/-/commit/d1b67558cbc06c449a0ae7b7c1694e277aef4a78.
>
> Is this OK to do so?
My
At 2024-03-31T22:32:49+, Stefano Rivera wrote:
> Upstreams would probably prefer that we used git repositories
> *directly* as source artifacts, but that comes with a whole other can
> of worms...
Speaking from my upstream groff perspective, I wouldn't _prefer_ that.
The distribution
At 2024-04-11T15:37:46+0100, Colin Watson wrote:
> On Thu, Apr 11, 2024 at 10:26:55AM -0400, Theodore Ts'o wrote:
> > Or, because some upstream maintainers have learned through, long,
> > bitter experience that newer versions of autoconf tools may result
> > in the generated configure script to be
39 matches
Mail list logo
