search

wez / wezterm

A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
https://wezfurlong.org/wezterm/
Other
16.76k stars 751 forks source link

[Minor] Debian/Ubuntu package contains invalid `Source` field in control file #2827

Closed cgrigis closed 1 year ago

cgrigis commented 1 year ago

What Operating System(s) are you seeing this problem on?

Linux X11

Which Wayland compositor or X11 Window manager(s) are you using?

xmonad

WezTerm version

20221119-145034-49b9839f

Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?

No, and I'll explain why below

Describe the bug

It is very minor :)

On Debian (and I believe also Ubuntu), there is a utility called debsecan that examines the packages installed on a system and generates a list of vulnerabilities. When I run it on my system with the wezterm package installed, I get:

$ debsecan
(...)
Traceback (most recent call last):
  File "/usr/bin/debsecan", line 1370, in <module>
    rate_system(target, options, fetch_data(options, config), history)
  File "/usr/bin/debsecan", line 1305, in rate_system
    raise SyntaxError(('package %s references '
SyntaxError: package wezterm references invalid source package 'https://wezfurlong.org/wezterm/'

Indeed, according to the Debian documentation, the Source field in the control file for a binary package is supposed to contain the related source package, not a URL. To be noted that this field is optional for a binary package.

To Reproduce

Install the wezterm and debsecan packages on a Debian or Ubuntu system, then run debsecan.

Configuration

N/A

Expected Behavior

debsecan without reporting a syntax error for wezterm.

Logs

No response

Anything else?

I did not try the nightly version because AFAICT this has not changed.

github-actions[bot] commented 1 year ago

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.