Bug#695188: 2017 patch review

[Brian Thompson]

Does anyone have time to review the patch that was submitted back in 2017?

2017 patch:
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=695188;filename=0001-Fix-695188-intelligent-add-of-Bug-XX.patch;msg=60

-- 
Brian Thompson 


signature.asc
Description: This is a digitally signed message part

Bug#1007922: false positive spelling: substract and subtract is both correct

[Brian Thompson]

I like the idea of keeping the spelling correction in place.  I've never seen 
"substract" being used.  Keeping the correction reduces ambiguity and keeps 
language consistent.

Motion to close.

Sincerely,

Brian

publickey - brianrobt@pm.me - 0xC8F2EC48.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Bug#858039: lintian: Graph (SVG) files on https://lintian.debian.org/ lack tag name

[Brian Thompson]

I've submitted a PR to get this change in as proposed by Axel:

https://salsa.debian.org/lintian/lintian/-/merge_requests/455
-- 
Sincerely,

Brian


signature.asc
Description: This is a digitally signed message part


publickey - brianrobt@proton.me - 688c834d.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Bug#907576: . dream -- A Software Digital Radio Mondiale Receiver

[Brian Thompson]

Garie,

TL;DR Use an IDE or text editor on your machine.

Local IDEs/text editors are used to develop the vast, vast majority of
software.  Most developers develop on their own machines instead of in
the browser.  It doesn't make sense to develop in a browser-based IDE
(at least not yet) since they are missing vital functionality.  Whole
OSes can't be replicated in the browser, whereby the browser greatly
limits access to common development tools.

Best regards,

Brian

On June 15, 2021, GMiller  wrote:
> Hello Christoph
> >Re: GMiller > For  the subject project, I have encountered a
> roadblock while attempting to use the 'Salsa Web Terminal'. I filed
> Gitlab Issue 233 (see attachments) seeking information to prepare a
> 'gitlab-webide.yml' file (I searched but could find no documentation
> on it). The response to 233 >says "To upload designs, you'll need to
> enable LFS and have an admin enable hashed storage". 
>  >>Sorry, I can help you with packaging hamradio software, but please
> use a normal editor like everyone else. There is no need to bother
> with funky web stuff, especially if it doesn't work out of the box.
> Christoph
>
> I am not sure I understand your comment. Are you saying in effect,
> don't use a Salsa IDE to build/test the project? Instead use an IDE on
> my local machine to build/test and develop any code changes? Is that
> how most Salsa projects are doing it?
> Thanks for your patience
> Garie Miller wb9awa
> Sent with ProtonMail  Secure Email.

Bug#951374: gh cli -- Getting it ready

[Brian Thompson]

Is anyone getting the gh CLI tool ready for packaging?  If not,
I can adopt it.  I use it quite heavily and am fairly familiar
with its development team if I have any questions.
-- 
Best regards,

Brian

Bug#990024: libxrandr2: xrandr shows HDMI-connected display as DP

[Brian Thompson]

Package: libxrandr2
Version: 2:1.5.1-1
Severity: normal
Tags: d-i

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

-- System Information:
Debian Release: 11.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-7-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libxrandr2 depends on:
ii  libc62.31-12
ii  libx11-6 2:1.7.1-1
ii  libxext6 2:1.3.3-1.1
ii  libxrender1  1:0.9.10-1

libxrandr2 recommends no packages.

libxrandr2 suggests no packages.

-- no debconf information
-
I used the Debian Bullseye non-free xfce-firmware installer.  After
completing the installation, I plugged in my external 144Hz monitor into
an HDMI port, but xrandr shows it as being connected to DP-1 instead of
HDMI-1.  Additionally, the refresh rate for the default resolution
(2560x1440) is set at 59.98Hz instead of 144.00Hz, with no option to set 
a higher refresh rate.

This is more about reporting that xrandr shows my HDMI-connected monitor
being connected with a DP adapter.
-- 
Best regards,

Brian T


signature.asc
Description: PGP signature

Bug#926175: apt-listchanges: only a single changelog is shown when multiple packages are updated

[Brian Thompson]

Every unexpected behavior is a potential bug. We shouldn't close this bug
yet.  Nicholas, are you still seeing this behavior?

-- 
Best regards,

Brian T


signature.asc
Description: PGP signature

Bug#926175: tag moreinfo 926175

[Brian Thompson]

tags 926175 moreinfo
thanks
-- 
Best regards,

Brian T


signature.asc
Description: PGP signature

Bug#990427: apt-listchanges: Invalid format text for mutt

[Brian Thompson]

Package: apt-listchanges
Version: 3.24
Severity: normal

Dear Maintainer,

After performing an installation of a previously uninstalled package,
apt-listchanges reported an error:

"Invalid format text for mutt"

The package still installed, but no changelog or NEWS was shown or
emailed out.

The expected behavior is that no error is thrown since the email_format
is set correctly, or if there is an error in my configuration (aside
from the email_format field), then that be pointed out instead.

-- Package-specific info:
==> /etc/apt/listchanges.conf <==
[apt]
frontend=pager
which=both
email_address=br...@hashvault.io
email_format=text
confirm=false
headers=true
reverse=false
titled=true
save_seen=/var/lib/apt/listchanges.db
no_network=false

[cmdline]
frontend=pager
email_address=br...@hashvault.io
email_format=text
which=both

[custom]
frontend=browser
browser=chromium


-- System Information:
Debian Release: 11.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-7-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages apt-listchanges depends on:
ii  apt2.2.4
ii  debconf [debconf-2.0]  1.5.75
ii  python33.9.2-3
ii  python3-apt2.2.0
ii  python3-debconf1.5.75
ii  sensible-utils 0.0.14
ii  ucf3.0043

apt-listchanges recommends no packages.

Versions of packages apt-listchanges suggests:
ii  chromium [www-browser]90.0.4430.212-1
ii  edbrowse [www-browser]3.7.7-2
ii  firefox-esr [www-browser] 78.11.0esr-1
ii  kitty [x-terminal-emulator]   0.19.3-1
ii  links [www-browser]   2.21-1+b1
ii  lynx [www-browser]2.9.0dev.6-2
ii  mlterm [x-terminal-emulator]  3.9.0-1
ii  palemoon [www-browser]29.2.0-1.gtk2
ii  postfix [mail-transport-agent]3.5.6-1+b1
ii  python3-gi3.38.0-2
ii  xfce4-terminal [x-terminal-emulator]  0.8.10-1
ii  xiterm+thai [x-terminal-emulator] 1.10-2+b2
ii  xterm [x-terminal-emulator]   366-1

-- debconf information:
* apt-listchanges/email-format: text
* apt-listchanges/confirm: false
* apt-listchanges/save-seen: true
* apt-listchanges/reverse: false
* apt-listchanges/email-address: br...@hashvault.io
* apt-listchanges/no-network: false
* apt-listchanges/which: both
* apt-listchanges/headers: true
* apt-listchanges/frontend: pager

Bug#989496: apt-listchanges: Error output if choosing to not continue after reading list of changes

[Brian Thompson]

Tia,

Thank you for reporting this bug.  I can confirm that this is an issue:

apt-listchanges: Do you want to continue? [Y/n] n
apt-listchanges: Aborting
E: Sub-process /usr/bin/apt-listchanges --apt || test $? -lt 10 returned an
error code (1)
E: Failure running script /usr/bin/apt-listchanges --apt || test $? -lt 10

I believe I have found the issue and have a fix ready to go.  I'll
set the status to pending.

-- 
Best regards,

Brian

Bug#990508: RFS: apt-listchanges/3.24.1 [ITA] -- Show new changelog entries from Debian package archives

[Brian Thompson]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for a package I made a fix for,
"apt-listchanges":

* Package name: apt-listchanges
  Version : 3.24.1
  Upstream Author : Brian Thompson 
* URL : https://salsa.debian.org/briant/apt-listchanges
* License : GPL-2+
* Vcs : https://salsa.debian.org/debian/apt-listchanges
  Section : utils

It builds those binary packages:

  apt-listchanges - package change history notification tool

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/apt-listchanges/

Alternatively, one can download the package with dget using this
command:

  dget -x 
https://mentors.debian.net/debian/pool/main/a/apt-listchanges/apt-listchanges_3.24.1.dsc

Changes since the last upload:

  * Fix error message being thrown when choosing not to proceed on
confirmation (closes: #989496).
  * Update maintainer to myself (closes: #981890).

Best regards,
--
  Brian Thompson

Bug#986840: apt-listchanges fails to parse status files with ^M characters; should use apt_pkg.TagFile, not write its own parser

[Brian Thompson]

> As reported in
> https://bugs.launchpad.net/ubuntu/+source/apt-listchanges/+bug/1854772,
> apt-listchanges
> fails to parse status files that contain carriage return characters, as
> Python normalizes the line endings.

I'm tracking the downstream bug in Ubuntu as well as this one.

> Instead of writing its own ad-hoc parser, apt-listchanges should use
> apt_pkg.TagFile instead.

I did a little bit of digging into how to rewrite the parser with your
suggested changes.  I agree that apt-listchanges should not be using its
own parser, especially since a standardized one exists in apt_pkg.

Preliminarily, I have these changes in mind for
apt_listchanges.ControlParser.readfile() (spacing adjusted for brevity):

```python
...
try:
  with apt_pkg.TagFile(file) as tagfile:
for section in tagfile:
  self.stanzas += [ControlStanza(x) for x in section]
except: ...  
```

There also, at the very least, may need a change to be made to
apt_listchanges.DebianFiles.ControlParser.readdeb() as well.  I'm hoping 
that we can avoid rewriting some of the classes in
apt_listchanges.DebianFiles, namely ControlParser and ControlStanza.

If you have suggestions on how the change would look, please let me
know.

-- 
Best regards,

Brian T


signature.asc
Description: PGP signature

Bug#986840: apt-listchanges fails to parse status files with ^M characters; should use apt_pkg.TagFile, not write its own parser

[Brian Thompson]

Julian,

I didn't see that you cloned this bug and assigned it to dpkg and that
the bug is no longer in apt-listchanges.  I still think that your
original proposal for apt-listchanges is relevant and is a change worth
making.
-- 
Best regards,

Brian T


signature.asc
Description: PGP signature

Bug#939287: Add urgency level separators

[Brian Thompson]

On Tue, 03 Sep 2019 03:37:58 +0800 =?utf-8?B?56mN5Li55bC8?= Dan
Jacobson  wrote:
> Man page says 'The groups are sorted by the urgency of the most urgent
> change, and than by the package name.'
> 
> Alas, that looks like
> 
> A
> B
> C
> A
> B
> A
> B
> 
> to the user. So perhaps add
> 
> --urgency=high:
> A
> B
> C
> --urgency=medium:
> A
> B
> --urgency=low:
> A
> B
> 
> separators, so it would all make sense.

I like the change you proposed.  I don't think that would be too hard to
do given that the changes are already sorted in order.  This would
definitely improve readability IMO.
-- 
Best regards,

Brian T


signature.asc
Description: PGP signature

Bug#990508: RFS: apt-listchanges/3.24.1 [ITA] -- Show new changelog entries from Debian package archives

[Brian Thompson]

On Sat, Jul 03, 2021 at 12:50:17PM +0200, David Kalnischkies wrote:
>Hi,
>
>On Wed, Jun 30, 2021 at 06:13:14PM -0500, Brian Thompson wrote:
>>   * Fix error message being thrown when choosing not to proceed on
>> confirmation (closes: #989496).
>
>If I understand your fix correctly, you have broken the "no"
>functionality as the Pre-Install-Pkgs hook has to fail for apt to
>actually stop… if they are successful apt will continue with what it was
>initially told to do, which seems not inline with what "no" was supposed
>to accomplish… could you clarify?

I didn't realize that the error message I essentially got rid of was
intended functionality.  I did some rudimentary testing of the change,
and if "no" was selected then any packages with a changelog entry aren't
updated, but everything else is.  Still, in hindsight, that could break
the existing package if dependencies are updated and the source package
is held back (that's definitely not what I intended).  I should have
tested more thoroughly, but I can revert the change.

I think the bug that was referenced by that fix shows that [at least]
some users were confused by the error message, and didn't realize it was
intended functionality.  Perhaps cleaning up the error message a bit so
users aren't confused by it (which may lead to erroneous bug reports) is
a good idea.

>(I don't know apt-listchanges code nor do I use the confirmation
> functionality of it, so I could easily be entirely wrong)

I'm pretty new to it as well.  I've only read through the code one time.

>(That seems more like we should have a way for the hooks to tell apt to
> gracefully wind down, but that doesn't exist so far)

That would be ideal.

>Could I interest you in joining the apt-team and maintain listchanges as
>part of it? I am personally not much help than it comes to python, but
>Julian might. Mailing list is de...@lists.debian.org and/or you can join
>our IRC channel #debian-apt.

I would be interested in joining the apt-team, and I think that makes
more sense than making "rogue" contributions outside of the team's view.

>I also note that your changelog targets unstable, which might be fine if
>you want to fix the mentioned bug and consider it RC (I am not so sure),
>but the churn in the package (= reflow of the pt.po and pot file) will
>make the release team unhappy.

That's good to know.  Thanks for pointing that out.  This is my first
contribution.

>Looking at your git history, all this should not be in one single commit
>either – individual commits with proper titles and metadata will help
>you even: You wrote the changelog by hand, git-buildpackage can do this
>for you...
>
>As a bonus, a week later looking at the history you will still know at
>a glance what happened without remembering (or looking up) cryptic
>bugreport numbers first – not to mention others. With the data in place
>you could then also add a hook to salsa which automatically sets
>bugreports to pending after a push of the related commit and many more
>fun stuff.
>
>(It is of course not required, even many upstream projects use "fix #42"
> as commit message and are happy and successful. So if that works for
> you fine, I am just trying to nudge you to try an alternative which
> works better for me, many others and perhaps also you)

Also good stuff to know.  I will take your advice and follow in others'
footsteps.

+++
In the meantime, I will take a closer look at the bug reports to see if
there are any quick wins there.  That way I can proceed with the
adoption of the package.

Lastly, I'll join the IRC channel and look to join the apt-team, as you
suggested.

Thanks, David!

-- 
Best regards,

Brian T


signature.asc
Description: PGP signature

Bug#990508: RFS: apt-listchanges/3.24.1 [ITA] -- Show new changelog entries from Debian package archives

[Brian Thompson]

+Tia, the bug reporter for #989496.
-- 
Best regards,

Brian T
B.S. Computer Science 2014 (Truman State University)
  Minor Stasitics
  Minor Chemistry
  Minor Mathematics


signature.asc
Description: PGP signature

Bug#989496: Looking to change the subject

[Brian Thompson]

It was brought to my attention by David K. (thank you, David), that the
what you are seeing is intended functionality.  I proposed in the email
thread with David that we could improve the error message, since right
now it may be confusing to users that it is actually expected behavior.
A cleaner, clearer error message should resolve any confusion.

I will CC you Tia.

-- 
Best regards,

Brian T
B.S. Computer Science 2014 (Truman State University)
  Minor Stasitics
  Minor Chemistry
  Minor Mathematics


signature.asc
Description: PGP signature

Bug#990508: RFS: apt-listchanges/3.24.1 [ITA] -- Proposed changes

[Brian Thompson]

David,

I'm thinking about the first line in debian/apt.conf to:

```
DPkg::Pre-Install-Pkgs { "/usr/bin/apt-listchanges --apt || test $? -lt
  10 >/dev/null 2&>1"; };$
```

adding the ">/dev/null 2&>1" in order to suppress dpkg errors in
apt-listchanges during the Pre-Install-Pkgs hook.  By doing this, the
original functionality will be preserved while at the same time piping
the misleading dpkg error message to /dev/null.  apt-listchanges will
still preserve its error message--"Aborting".

What do you think about this approach?

The alternative is to close out this bug since it is intended
functionality and leave it as-is.

-- 
Best regards,

Brian T
B.S. Computer Science 2014 (Truman State University)
  Minor Stasitics
  Minor Chemistry
  Minor Mathematics


signature.asc
Description: PGP signature

Bug#869748: Cloned and assigned to aptitude

[Brian Thompson]

I cloned this bug and assigned it to the aptitude maintainers.

The bug number is #990747.

-- 
Best regards,

Brian T
B.S. Computer Science 2014 (Truman State University)
  Minor Stasitics
  Minor Chemistry
  Minor Mathematics


signature.asc
Description: PGP signature

Bug#989496: Tagging wontfix

[Brian Thompson]

Since this is expected behavior, I am tagging as "wontfix".

I don't think it's a good idea to suppress the error message.
apt-listchanges gives an "Aborting" message prior to throwing the error.

-- 
Best regards,

Brian T
B.S. Computer Science 2014 (Truman State University)


signature.asc
Description: PGP signature

Bug#990508: New RFS: 3.25 (includes NMU update and maintainer update)

[Brian Thompson]

New version proposed for sponsorship at:
https://mentors.debian.net/package/apt-listchanges/

This is a new release of apt-listchanges where I incorporated an NMU commit into
the new version.  I didn't think I would need to release this as an NMU version
since I also updated the maintainer.  I thought that was a good enough reason to
skip straight to the 3.25 version instead of 3.24+nmu1.

I suppose it could be split into two separate releases, one for 3.24+nmu1
(first) and a later one for the 3.25 version (my changes).

In other news I have been triaging bugs in my spare time.
-- 
Best regards,

Brian


signature.asc
Description: This is a digitally signed message part

Bug#802368: ITA: docbook-xml

[Brian Thompson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

retitle -1 ITA: docbook-xml -- standard XML documentation system

- -- 
Best regards,

Brian T.
-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEE9fpVo96/flopdKOfgw2Ncu3Nhn0FAmEPCekTHGJyaWFuQGhh
c2h2YXVsdC5pbwAKCRCDDY1y7c2Gfe8VEACrpLu2smZo7oiQs2uhRyDAzj+iaScg
9C3kmOcnit9VVhuPD+VXi8+nkL5lsRvmgHuLuI9aKfHXRVgie/yswrpZIQsUA/v/
kLLcEcCUCnEfQs15fru56TT3zby2Yyzrcpy7f16aVo8urZcu6izwgJDyawzrEz/L
CpX1oFa2dIJVO1kJX72z1QGCLnQkXuy+MyvmM3wvRfNcH5DSU3PYKOqGAKT5zStz
fyuinvS8akOiTrm8AhXQmDGp1shet3jP5N5IOPqHcoUu/wNmUs2BYDY91NtIXNFq
b8sYNTM5zEBDlf2MwgcyCyIzF1Zcf/GRUW0JgxMqrUsOjgaVVvGamgzyhil6hOL3
Fd4PAa2u4NhVlq/lRumCSGA9fW7O2iRZ/rj4vO1c8YaiGKD3wqaXJWeLFILvngQk
F3nvxi4qaz0oMXlYW5Jjy4lX3q/WgVUBLpXayS7DuV7o7JDhC6Y8NHrTuruR8ckn
F4Lrvj7lBJNlaTI/2uWy7o7RPuOOE7zGJWQyAeyYKQh9KlTwAy1H9d/QRh5sLv3g
/1uVu/ZNzm1Rtt3xYcHEDfkgVuvuZCmiH0WNsxbyA46quyjGDmEP15MkThrzESFv
VPWem7Lrp/I2MRb6Drwr8c3nlkPerRkbVyZS8bFDe64n/3+F+Orp2YD7WnseKd04
9ui1uOttuJXhFQ==
=CjbS
-END PGP SIGNATURE-

Bug#802370: ITA: docbook-xsl

[Brian Thompson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

retitle -1 ITA: docbook-xsl -- stylesheets for processing DocBook XML
- -- 
Best regards,

Brian T.
-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEE9fpVo96/flopdKOfgw2Ncu3Nhn0FAmEPClETHGJyaWFuQGhh
c2h2YXVsdC5pbwAKCRCDDY1y7c2Gfd7RD/9qIBu3K1iq1mjZ5YibRc85HonHrOJb
UlHlQ7dRHPlFjYvbXsYKVZpdzQTtz3LkZvgFvldFC0LxYtWBNQzxn4X3SgGbNNRB
b/P0cMRCgHCV0EG6B6q0NhM05+t0sPyscnu4VbjwlHlEFNrr3OP0uJJh/MbSjuST
1MG1k10Ihu+B6dOFK4Mq5Fl6LqNgUoSqXcKOib72W8vgXxkwKWmoBvbc0qRGMgGn
vYcMnwaISsHLIfwmFNQaQ+0HVhX3sTrvI1273K5fdi9hAjd/nA5i74UigQwpvb1l
gvzOjfFykK7E0aKtsEGdC3NHLd9lm17JP50iJYAZZz+JH79sj+M0TCORo8SG/lOv
6p3gRrzgX5RAZPDWXDBdJwE8rNDZQCeYIBSnsui9SpyRsjH/7dasSU1aoSigOB+U
oJcof1Q4hbXA4Viam0DHvm1EzIF97R5ZBFgGPQFnD9qpRk4pckMGD0/tnBDHcCAZ
u9oSNQCmCZ02gLSW4CiYbQ+LiGWWw6LEUoPRjhK188KqjTm6A1sPs7cK1Ibe9r/z
giT6tCVa3LTyFG0hO/FMiq73owLVzOJ9UwWzq7+NRceCQIENkZkNmQ9g2Lf6Fol2
Ul2jQDjJ755MrhspW9zO1crLsjs14meKWAAExleYmmOnpSK2cB6wSjS/VTrwdZAO
KgX+FOqMhwK9FA==
=lfHp
-END PGP SIGNATURE-

Bug#951374: RFP: gh -- the GitHub CLI

[Brian Thompson]

> I personally find that "gh" is quite short name for a package that
> will go into a general purpose software catalog like Debian repository. Would
> you mind choosing something like "github-cli" as source and binary
> package name and mentioning the sortcut "gh" in a package description?
> So anyone could find the program by means of `apt-cache search`.
> Acronyms gh and gn (which stands for Google's Generate Ninja) are
> visually similar, and I'm afraid they are easily confused.
>
> What do you make of this proposal?

I like that proposal and think it makes a lot of sense. `gh` does seem
too short, and while easy to identify for current gh users, maybe it
will be more difficult to find in apt for new users. Also, as you
mentioned, a namespace clash in the future seems like an uncommon
occurence.
-- 
Best regards,

Brian T


signature.asc
Description: PGP signature

Bug#434986: Tagging wontfix

[Brian Thompson]

Since this OP has found another apt cron package to serve his needs,
I've tagged this bug as wontfix.
-- 
Best regards,

Brian T


signature.asc
Description: PGP signature

Bug#76500: Tagging as wontfix

[Brian Thompson]

There's two separate wishlist items in this bug, split them up into two
separate bugs if you still want this (or anyone for that matter) so that
each one is easier to track.  I'm keeping this bug open for the original
request.

I'm going to tag this as wontfix for now.
-- 
Best regards,

Brian T


signature.asc
Description: PGP signature

Bug#111013: Cannot reproduce

[Brian Thompson]

I am unable to reproduce the fix that was mentioned in this bug.  I
tried with less and running `export LESS="-r $LESS" and
`export LESS="-R $LESS"`.

Marking as unreproducible for now.
-- 
Best regards,

Brian T


signature.asc
Description: PGP signature

Bug#111013: apt-listchanges fixes

[Brian Thompson]

On Mon, 12 Nov 2001 22:34:27 -0500 Matt Zimmerman  wrote:
> I must have completely overlooked the documentation fixes in your bug
> report; I thought you were just adding documentation for the option you
> added in your patch.  I've applied them in CVS now, thanks.
> 
> -- 
>  - mdz
> 
> 

Bug#111013: apt-listchanges fixes

[Brian Thompson]

On Mon, 12 Nov 2001 22:34:27 -0500 Matt Zimmerman  wrote:
> I must have completely overlooked the documentation fixes in your bug
> report; I thought you were just adding documentation for the option you
> added in your patch.  I've applied them in CVS now, thanks.
> 
> -- 
>  - mdz
> 
> 

Bug#951374: RFP: gh -- the GitHub CLI

[Brian Thompson]

On 0814, Paul Wise wrote:
>
>Could also add a Provides: gh so it is installable with the short name.
>
>I would definitely like to have this in Debian, but can't help with it.
>

This would be ideal. Is there any benefit of renaming the package to
something other than "gh"?  I can help with this during the next week.

-- 
Best regards,

Brian T


signature.asc
Description: PGP signature

Bug#514865: apt-listchanges: GTK+ window should not steal focus, and only appear if there is anything to show

[Brian Thompson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On Wed, 11 Feb 2009 11:11:57 -0200 Gustavo Noronha Silva  wrote:
> Package: apt-listchanges
> Version: 2.83
> Severity: important
> 
> The GTK+ frontend has a very bad behavior: it will display a window
> and quickly close it if there is nothing to show. When the window is
> displayed (either because it has stuff to show or not), the window
> simply pops up in front of anything you are doing.
> 
> It should instead show in the background requesting attention (so that
> its taskbar button will pulse no matter in what virtual desktop you
> are). And should, of course, only display the window if there is
> something to show.
> 

There have been a lot of changes to apt-listchanges since 2009. Can you
confirm if this is still an issue for you?

- --
Best regards,

Brian T.
-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEE9fpVo96/flopdKOfgw2Ncu3Nhn0FAmEYUUATHGJyaWFuQGhh
c2h2YXVsdC5pbwAKCRCDDY1y7c2GfTzVD/9oIRRiWVy7OtLrrj4i4GmYH/4HHf03
ncC/j1U2TxFYmWVpuP4AW1Ifv8tKsGormHOOJNVAhzkiDSvPdaWE0xZbHHNllAyx
k8XHmzF24xkyOm42k+j7v7xB6VUM8WPBDZQhfyRIPG/lBnsVLyW0+2JtlwaJuH2e
YNnEOGMVasK9LyZKQytCl2OEbFx7KJdbzShxwv6iELJ/uAxJdhpoeuRKMSBQ4aG4
u6/aRXPgSNlZ2jfwbuFVqYhakjrq0sCVPNu2joIQCwPHtY6Bw7JaHR9A15MWxKtJ
pC6T9Xrs1mLF4rSGaBpj2E1nYo1jWyUwTbm0cJv+B0YnCBs0OAwsIagjYNO87YRK
SocnBT7BrfnoO24gdFkdBkgWLGLcFMPYsjr7CUmmGWi69d+3U/8mp/KSXrh5L0u8
+RIvcqn8N6GvReJ6PudMaPCS/QavbaI/ljGOkJ66yspU7Si10UkfQCw8whir0GLm
U8bl/JI+94poMdCs4J2mMaaITpfISIr7T9WiJMbIhucEyKyS04opKjvGD6jPaKcr
MsQsHZeeUHmfViH02Ds3Aor9MLaEHEQpdppM5wfy3xw8fRq7FWEZQIYb6gaGvFLX
h315bJptP+Zc0IkKe6N2cEyMFZnDZylmcxUbW37buX0XgV/ycEWV7BzjWwNRbb4s
yOVj2Wa3SpszFQ==
=0HIg
-END PGP SIGNATURE-

Bug#951374: RFP: gh -- the GitHub CLI

[Brian Thompson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On Sat, 14 Aug 2021 14:18:34 -0400 =?utf-8?Q?Antoine_Beaupr=C3=A9?= <
anar...@orangeseeds.org> wrote:
> 
> It's not on the package name, but there's already a clash on the
binary
> name, which we should be mindful of:
>  gitsome provides direct integration with GitHub and GitHub Enterprise
in
>  a terminal.
> 
> Since it's a git (and github, even!) related tool, we might even want
to
> Conflict with it directly...

Since there is already a package that uses that binary name, who should
change it? Do we follow a first-come first-serve binary name reservation
strategy? I don't think it's a big deal to change the name.

I'm not sure what to rename it to. I don't like binaries with long,
descriptive names, but I don't know what we could use that is short. I
will raise awareness about this issue with the upstream developers.
- -- 
Best regards,

Brian T.
-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEE9fpVo96/flopdKOfgw2Ncu3Nhn0FAmEZ7NQTHGJyaWFuQGhh
c2h2YXVsdC5pbwAKCRCDDY1y7c2GfeX5EAChFZ4pCKTj1uvCuyAxCzr12dfdfIqC
U27Bc1UwT5DAKs9T2EjihTkhstinwN3ZKLmOOznH1+lnmbdlXccYRtV4BZvu3diD
iyzP4t+5voLnxViYzO8WjHcxSlA7qNUY1/16nmOuTvrNmpaxS/54gjOyFXjdOWVc
CGCHUm2TG3aMTaW+OfOizBG+T+ThNNrkRg/8cKStgcR2vB8gwa/gJdT4qccsLCHv
ufrxVg3p7VzjVvBD7W4Z5uczqwnYR7/3FK3M65FH1TKZTCxDIv3BYGKIIEM0nXnJ
sLzFCucItVVi/Cc7CJf/sH9T49BzVfL+GTGFbDhue70+NpfOa++z7p22qq211Zvd
5E2vRXSLpQVmMY8QZy8+xDgBvi1CP1hBx98XbSE1RquV902naHowsFxTa4nkAPiK
nYU81R8TbLGwdPUXO/SgnSLQ9IlA7IotwfXmEhPAge8rYIR+2TtE0Da6ROeT8Tj4
lDiH9p6RS78Y49wihatMkpxKNkypQdUwq5AZb8p3b2j/h7hFz6l9m0TcAxxkggjZ
HPFDt0n0hGr6KzAtemFMP04OyqurMVCEtwn84ySmUI3Sy9i42uT36c2M7+TOd2iu
C2R/kXr7ZJ9fWxwpAkyv4/4rPqu2AwSeCluzUPRLTxR/8zqlTIwGK3tDlNQH3bQD
aTB5+YZvyIHIeg==
=YHqO
-END PGP SIGNATURE-

Bug#754831: [apt-listchanges] Program Crashes On Konsole Sessions

[Brian Thompson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Which pager are you using, or does this occur for all pagers in KDE
Konsole?

- -- 
Best regards,

Brian T.
-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEE9fpVo96/flopdKOfgw2Ncu3Nhn0FAmEZ7d8THGJyaWFuQGhh
c2h2YXVsdC5pbwAKCRCDDY1y7c2GfeUwD/9VG1VdWeT/oW07i3R5HLYddBX34Igk
9YbB9IzXNt+RqG1IR1Qz6ZtJkwokykknO+GOEOIqIfjiVn8Y0DO1FQhqxG1K/z5z
XKCuX/+A8HD751Syhf+wa+2TuVY6zaNsO+8HAK4vOyMWrUN9UTP9YNEEYvv1YF89
EjlCVrWvqaiAlbVae6h78Wmm37cfcTgSb1daGNQEdh/VNKgqWJ2X8zOW7kFsG1ch
WSjvj2Ysd1+w70fPCQug+C670JYamILGEAOyrwogBqwqXXGvCGY9ofjTGsz09ayh
Q5IHEi1BdakcMwMdMKeHsxNKFMMEcvKLV5YMp2RF+o+E8PrK5ZmFTkGIs1H0N4qX
Cf9LQ4qFDIhlh1j0UL6wBgZOnZt2V+8Nolau4wJZxhP2m4UAHTWM61d53qP/y7Dk
ONiMMiP4d6Bn4DEVpRbcv1XMw6Dre2Pn0fMEZFee1HkPs7dCBIext1DYaQ5aP4iF
jn5zqszXOGimuacDdAXOwQK270hdcM7W3u4JK12VWtxAXJmeMoELkZmG+OTcsxWD
FxfzGPEGmU1wPvoS4ou2tgCaxELcEXZGJHWvkpSRjOWLIlIDyeHbywHK/1s8cdAL
2AZvIuWyXuc5akUbMyXueMjMQ5yLJE/RA7lcMo7wB+LDEDmysjWZpOaRFF2LSHtM
drFWZhcF+8hH2A==
=lejN
-END PGP SIGNATURE-

Bug#951374: RFP: gh -- the GitHub CLI

[Brian Thompson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On Mon, 2021-08-16 at 21:27 -0600, Anthony Fok wrote:
>  NEW queueOn Sun, Aug 15, 2021 at 10:45 PM Brian Thompson
>  wrote:
> > 
> > Since there is already a package that uses that binary name, who should
> > change it? Do we follow a first-come first-serve binary name reservation
> > strategy? I don't think it's a big deal to change the name.
> > 
> > I'm not sure what to rename it to. I don't like binaries with long,
> > descriptive names, but I don't know what we could use that is short. I
> > will raise awareness about this issue with the upstream developers.
> 
> Hi Brian,
> 
> First of all, thank you for volunteering to help with the packaging of
> GitHub CLI.
> 

Anthony,

Thank you for being intimate with the details. 

> Here is my understanding:
> 
> Now, you might run into a problem when actually trying to name the
> package "github-cli" (or even "gh") because dh-make-golang 0.4.0 does
> not allow for overriding the package name.  For example:
> 
> dh-make-golang -type p -pristine-tar github.com/cli/cli
> 
> would name the package "cli"... I am working on packaging the latest
> dh-make-golang and will try to add a flag to allow overriding the
> package name, to be uploaded as dh-make-golang 0.4.1 or 0.5.0.

It sounds like this functionality is required for what we are trying to achieve.
I am not very familiar with the golang family and its surrounding infrastructure
regarding Debian. Perhaps I am not best-equipped to package the github-cli tool,
but I am always willing to learn.

> Then there are the yet-to-be-packaged dependencies.  Just so that you
> know, the following packages that github-cli depends on have already
> been packaged but currently sitting in the
> https://ftp-master.debian.org/new.html NEW queue:
> 
>  * golang-github-yuin-goldmark-emoji 1.0.1-1
>  * golang-github-muesli-reflow 0.3.0-1
>  * golang-github-shurcool-graphql 0.0~git20200928.18c5c31-1
>  * golang-github-shurcool-githubv4 0.0~git20210725.83ba7b4-1
> 
> I'll report back here if I were to package and upload more of these
> dependencies so as to avoid duplication of work.
> 

It sounds like we should pause the github-cli technical packaging work until
dependent features and packages are added to the ecosystem. Would you agree with
that? I'm not seeing any BTS tags specific to RFPs (or bugs in general) for
marking it as "blocked", as we would say in the corporate world. Although I am
not sure that is even necessary.
- -- 
Best regards,

Brian T.
-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEE9fpVo96/flopdKOfgw2Ncu3Nhn0FAmEbQYcTHGJyaWFuQGhh
c2h2YXVsdC5pbwAKCRCDDY1y7c2GfaNpEACgqGGp/BsUjnGpALGzNbMtqY2P4b3d
EqhxUmQdEzDPKw7g4ajyYkFiDm9Djgvz2g3R6jgYcjuOlcjeI3YOZNtJMmriUw7p
CM4jgaaXn/YvKFQxqNWD7GTsWlJnej4mCmebiRTseG3MX8BEHb4Ukndiy3pR2vXx
nhHVq+JJZsti8goTcROgToG8a0lH+rUj8yc0uN/e2JQcLCHOjXZdgUDQQzUVW+3C
iVMJ1tp88vrTpXn04TxMdHIyGbWh8SMFv9Q3+F4HyWBc9UiYq4kmOw1US/0YL8PQ
rwiGXzNxS6BoYZ9W0EtRwy27asBJDpfRsGOFzqzVK+fSGk7teThL3sS8SoxR1XjQ
Z7sebgTsY+A0b8+YYR8UOZb1Ei616cmD/m2bKntHQHzTMQw1rmWJgKxeoh9ARv91
b1PUbZndsSDbOukj+nt+gD+NayAwJDceTYZ3hm5FnE4tADPWCkeSixQVBafNM1i5
ZY02qCqtP0Z37lRsAOj53jTweOmSm4Fv5sJG/FtqHEAnd/fNd17KT5ggii6uPEhD
vdyBdtlB5K8ZboT7f2HtHuoOkAHcLPKU6rq0kAI+43Dt0nw4XTSWoB3AH2dNW4ii
wKqxgOKo4j+mxc6TZckn4xNbRXrB1dGEwu7/HuRg//+EsdqNW0PWNEqpNxIRNHgz
NhR8XUSX3KW71Q==
=Bui2
-END PGP SIGNATURE-

Bug#365427: Autotests for apt-build utility

[Brian Thompson]

On Thu, 15 Nov 2018 23:40:07 +0300 =?UTF-8?B?0JrQvtC70Y8g0JPRg9GA0YzQtdCy?=  wrote:> I intend to do some refactoring of apt-build, but first I'd like to> write autopkgtests for the package. I have two versions of a simple test> case for install command, and I still can't decide what language use for> tests. In attachment you'll find two identical scripts in Bash and Perl.> Comments are welcome!> > It'd be good to write full tests before new year and buster freeze.> > To be clear: I'm not going to adopt the package yet, because I'm unsure> that I have enough time for this work.>  @Axel Beckert This is the message I was referring to from “2016”. I would like to adopt this package if no one else has. Best regards, Brian Thompson 

Bug#984736:

[Brian Thompson]

>Ideally a maintainer willing to help cron move forward would support the next>major task to be done: moving the Debian-specific patches into cronie and >providing an updated package for cronie replacement that can eventually>replace cron. I’d like to help out here if no one else has responded.  I can read repositories on Salsa but don’t have an account there yet since I’m not officially a part of the Debian org. >Please contact the current maintainer if you can help in maintaining and>improving cron. @Javier, I cc’ed you and I think what is Christian’s email which I pulled from the cron git history. Best regards, Brian 

Bug#987467: autopkgtest library fails with: FAIL stderr: pkill: killing pid 1764 failed: Operation not permitted

[Brian Thompson]

On Sat, Apr 24, 2021 at 01:06:04PM +0200, Chris Hofstaedtler wrote:
> Source: mosquitto
> Version: 2.0.10-4
> Severity: serious
> 
> Dear Maintainer,
> 
> your autopkgtest appears to fail:
> 
> autopkgtest [21:45:54]: test library: [---
> pkill: killing pid 1764 failed: Operation not permitted
> make: Entering directory 
> '/tmp/autopkgtest-lxc.zrj4yodu/downtmp/build.er2/src/test/lib'
> [..]
> autopkgtest [21:46:36]: test library: ---]
> autopkgtest [21:46:36]: test library:  - - - - - - - - - - results - - - - - 
> - - - - -
> library  FAIL stderr: pkill: killing pid 1764 failed: Operation 
> not permitted
> autopkgtest [21:46:36]: test library:  - - - - - - - - - - stderr - - - - - - 
> - - - -
> pkill: killing pid 1764 failed: Operation not permitted
> 
> I do not quite understand what the pkill -x mosquitto is good for in
> the tests, but certainly it does not work.
> 
> Filing as serious, as this prevents migration to testing.
> 
> Chris
> 

I'm not a maintainer, but I see that in the code the command does what
it intends to do, checks out with the man pages although I haven't read
it myself:

# Tell Mosquitto to reload certificates and configuration
pkill -HUP -x mosquitto

Additionally, this code looks like it should work:

# Set ownership to Mosquitto
chown mosquitto: /etc/mosquitto/certs/server.pem \
/etc/mosquitto/certs/server.key

# Ensure permissions are restrictive
chmod 0600 \
/etc/mosquitto/certs/server.pem \
/etc/mosquitto/certs/server.key

But I think this is more accurate (omitting the ":"):

chown mosquitto /etc/mosquitto/certs/server.pem \
/etc/mosquitto/certs/server.key

Best regards,

Brian


signature.asc
Description: PGP signature

Bug#365427: [O: apt-build] Is this package worth adopting or has it been replaced?

[Brian Thompson]

On Sat, 17 Apr 2021 05:48:48 +0200 Axel Beckert  wrote:
> Hi,
> 
> No Body wrote:
> > Is this package worth adopting or has it been replaced by something
> > else?
> 
> There's nothing like it so far AFAIK. apt-src is close, but has a
> different focus (modification instead of compile-time optimization).
> 
> > I read the entire bug message history and saw that in 2016 there was some
> > development going on to replace the package.
> 
> I don't see which message you mean. In 2016, there were only control
> messages and spam in this bug report.
> 
>   Regards, Axel
> -- 
>  ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
> : :' :  |  Debian Developer, ftp.ch.debian.org Admin
> `. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
>   `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
> 
> 

Axel, switched my email address to one that I actually use. Going to start 
looking into this package more.
-- 
Best regards,

Brian

Bug#985669: Happy to help

[Brian Thompson]

> While I would love to package this myself, I do not work with
> JavaScript regularally (in part due to ecosystem problems like
> NPM's love of duplication).

I have some experience packaging JavaScript projects and could help you
out here.



signature.asc
Description: PGP signature