Details about package verilog-parser
Package uploads
Upload #1
Information
Changelog
verilog-parser (0.0.6-1) unstable; urgency=medium
.
* Initial release. (Closes: #1109250)
Comments
-
Hey,
Consider the 'Recommends' placement.
Regards
Phil
Phil Wyett at July 14, 2025, 10:28 a.m.
-
Hey,
Lintian:
I: python3-verilog-parser: wrong-section-according-to-package-name electronics => python
N:
N: This package has a name suggesting that it belongs to a section other than
N: the one it is currently categorized in.
N:
N: Visibility: info
N: Show-Always: no
N: Check: fields/section
Regards
Phil
Phil Wyett at July 14, 2025, 10:34 a.m.
-
Hi Phil,
pkg-electronics team suggested to do this:
> "Engineering;Electronics;" are used as application categories, they are non-standard, but categories such as (Education and Science) are completely inappropriate for the engineering applications maintained by the team.
> This course of action does cause lintian to give desktop-entry-lacks-main-category warnings, and those warnings are ignored.
> Also, extra-xdg-menus is to be added to the Recommends field (in debian/control) to provide menu categories for Electronics applications. "
Hence I've already added extra-xdg-menus in this upload. This package is however a python library but I'm packaging it for Debian Electronics Team hence I've used the electronics section.
Do you recommend going with 'python' section instead?
Regards,
Aryan Karamtoth
Aryan Karamtoth at July 14, 2025, 10:42 a.m.
-
Hey,
Copyright fun and games. :-)
* pyproject.toml:
# SPDX-License-Identifier: GPL-3.0-or-later
Did upstream miss the 'A' before the 'GPL'? :-)
* test.sh, 'lrc' output:
d/copyright | licensecheck
AGPL-3.0-or-later| CC0-1.0 test.sh
* Other 'lrc':
d/copyright | licensecheck
AGPL-3.0-or-later| AGPL-3 LICENSE
AGPL-3.0-or-later| AGPL-3+ src/verilog_parser/__init__.py
AGPL-3.0-or-later| AGPL-3+ src/verilog_parser/parser.py
AGPL-3.0-or-later| AGPL-3+ src/verilog_parser/test_data.py
Regards
Phil
Phil Wyett at July 14, 2025, 10:44 a.m.
-
Hey,
The section is OK, you may wish to add an ovverride for the lintian warning, but not major and you could leave it, all about personal dev/DD preference.
The 'Recommends' hould be with the 'Package' not 'Source' section.
Regards
Phil
Phil Wyett at July 14, 2025, 10:55 a.m.
-
s/hould/should - Yikes, busy and doing three things at once. :-)
Phil Wyett at July 14, 2025, 10:56 a.m.
-
Hey,
Your going to have fun working inside the Electronics Team. Just looking at bugs and how old the 'Standards-Version' is in a lot of the packages is a bit shocking.
Regards
Phil
Phil Wyett at July 14, 2025, 10:59 a.m.
-
Hi Phil,
Yes, its a typo in the upstream as evident in this file: https://codeberg.org/tok/py-verilog-parser/src/branch/master/pyproject.toml
Possible changes I have in my mind:
1. Fix the licensing in pyproject.toml and send the fix upstream as well as commit the changes to the package and rebuild at the same time.
2. Change d/copyright of * to AGPL-3+ but it will still conflict with the LICENSE
3. Put Recommends inside package
4. Write another copyright rule for test.sh
I'm still not sure how to deal with the conflict in LICENSE. Can you advise me about this?
> s/hould/should - Yikes, busy and doing three things at once. :-)
I'm sorry but didn't get you
> Your going to have fun working inside the Electronics Team. Just looking at bugs and how old the 'Standards-Version' is in a lot of the packages is a bit shocking.
Really? I've noticed that their mailing list is full of spam bots too but I got accepted into the team by one of the owners today so I assumed it's active and the packages are maintained properly.
Regards,
Aryan Karamtoth
Aryan Karamtoth at July 14, 2025, 11:01 a.m.
-
Hey,
You can add 'LICENSE' to 'debian/lrc.config' and it will be ignored when 'lrc' is run against the package.
I was looking at the bugs list for the team. Working within a team is something I recommend and I like you are doing it. You will do small changes on packages and you will make bigger changes - All good learning.
Regards
Phil
Phil Wyett at July 14, 2025, 11:06 a.m.
-
Hey,
In your list of possible changes, I would not bother with #1. I would just report upstream.
Regards
Phil
Phil Wyett at July 14, 2025, 11:30 a.m.
-
Hi Phil,
Thank you for the tip with #1.
I'm going to become an Electronics Engineer once I graduate out of college so Electronics and Science Teams are the perfect places for me to contribute as I'm a STEM major myself.
Coincidentally, I'm learning Verilog right now so I'm kind of focused on packaging Physics and Electronics related packages right now with a special interest in Verilog related ones.
I will soon work on the changes I mentioned and remind you when I make another upload containing the changes.
Regards,
Aryan Karamtoth
Aryan Karamtoth at July 14, 2025, 11:47 a.m.
-
Aryan,
I like your thinking and you will bring a level of practical knowledge that others do not have which will be a great advantage for the team. I hope you get as much out also working with the wide variety of folks who contribute to Debian.
Regards
Phil
Phil Wyett at July 14, 2025, 11:56 a.m.
-
Thank you for the words, Phil. It means a lot. I'm surely eager to meet more folks and attend the next DebConf myself as a speaker if my college allows me to.
I've also opened an issue in the upstream repository [1] informing the author regarding #1. The library was updated just a few days ago, hence I'm expecting a quick response as this is a small fix.
[1] https://codeberg.org/tok/py-verilog-parser/issues/6
Regards,
Aryan Karamtoth
Aryan Karamtoth at July 14, 2025, 1:50 p.m.
-
Aryan,
Debian doesn't generally use SPDX identifiers, though I wish it would. For reference the SPDX license list with their idebtifiers is at the link below.
https://spdx.org/licenses/
Regards
Phil
Phil Wyett at July 14, 2025, 2 p.m.
