Re: Debian maintainer does not forward bug reports

["Martin Mareš" <mj@ucw.cz>]

Cc: Guillem who is the Debian maintainer of pciutils; see below for
context.

Let us go through all outstanding bugs filed against Debian pciutils:

> #887113		pciutils: lspci does not detect sound for nvidia MPC67 on Pavilion DV9720us
> #775453		/usr/bin/lspci: "lspci does not detect nvidia geforce 210M on Asus UL80Vt"

These are likely kernel issues. Since they are a decade old, we should
ask the submitter for testing on a recent kernel.

> #656925		failure to detect PCIe Gigabit LAN

Not a pciutils problem, probably a missing kernel driver. It's from
2012, so it should be tested with a recent kernel.

> #774063		pciutils: update-pciids changes md5sum of pci.ids

This is specific to Debian. Another alternative would be to make
update-pciids store the downloaded file to /usr/local/share and let
libpci prefer this file over the one if /usr/share if it exists.

> #595328		/usr/bin/lspci: lspci reports wrong video ram size

It's from 2010, so I am not sure if it's worth investigating.

When a bug like this is submitted, please ask the author to provide
the output of "lspci -vvxxx".

> #640239		/usr/bin/lspci: lspci -t (-v) doesn't show bridges

We have rewritten the whole tree display code since this version,
I hope that this problem does not exist any more.

> #870000		pciutils: Debian Stretch freeze when I use "lspci"

Very likely a hardware bug. If it should be worked around, the right
place is the kernel.

> #924237		lspci shows wrong/misleading string instead of "Device xxxx"

Interesting... can you ask the submitter if they can reproduce it
with current pciutils?

> #1087569	pcilmr.8: Some remarks and editorial changes for this man page
> #1087678	pcilib.7: Some remarks and editorial changes for this man page
> #1099040	setpci.8: Some remarks and a patch with editorial changes for this man page

Bjarni, I assume that these are the bugs that triggered your message.
I don't see any Debian patches to pciutils man pages, so I will apply
your patches upstream.

> #585146		lspci: query the database for specific vendor/device IDs

This could be useful. I will consider adding this feature.

> #929984		lspci: please make -nn the default

I admit that it would help in some cases, but on the other hand,
it would make the default output more cluttered, so I don't think
it's a clear win.

				Have a nice fortnight
-- 
Martin `MJ' Mareš                        <mj@ucw.cz>   http://mj.ucw.cz/
United Computer Wizards, Prague, Czech Republic, Europe, Earth, Universe

---

> See
> 
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=pciutils;dist=testing
> 
> -.-
> 
>   Additional remarks.
> 
>   Mails from me to "submit@bugs.debian.org" are no longer acknowledged.  A
> Debian maintainer told me, that he would contact the mail administrator
> about me not wanting to send bugs upstream.
> 
> -.-
> 
> From "/usr/share/doc/debian/bug-reporting.txt.gz":
> 
>   Don't file bugs upstream
> 
>    If you file a bug in Debian, don't send a copy to the upstream software
>    maintainers yourself, as it is possible that the bug exists only in
>    Debian. If necessary, the maintainer of the package will forward the
>    bug upstream.
> 
> -.-
> 
>   For forwarding bug reports to upstream see:
> 
> https://www.debian.org/Bugs/Developer#forward
> 
> -.-
> 
>   I do not send reports upstream if I have to get an account there.
> The Debian maintainers have one already.
> 
>   If I get a negative (or no) response from upstream, I send henceforth
> bugs to Debian.