It's rust, not a Golang, mate.
Yeah everything would be rust :)
On July 10, 2025 4:12:46 PM UTC, to...@tuxteam.de wrote:
>On Thu, Jul 10, 2025 at 03:48:52PM +, Andy Smith wrote:
>> Hi,
>
>[...]
>
>> As an aside, sudo-rs is packaged as of Debian 13 (trixie, currently
>> testing) and I've been
As the name said, 'rs' stands for Rust, not Go, mate.
On Thu, Jul 10, 2025 at 06:12:46PM +0200, to...@tuxteam.de wrote:
> On Thu, Jul 10, 2025 at 03:48:52PM +, Andy Smith wrote:
> > Hi,
>
> [...]
>
> > As an aside, sudo-rs is packaged as of Debian 13 (trixie, currently
> > testing) and I've
On Thu, Jul 10, 2025 at 03:48:52PM +, Andy Smith wrote:
> Hi,
[...]
> As an aside, sudo-rs is packaged as of Debian 13 (trixie, currently
> testing) and I've been using it for a week now without complaints. sudo
> fans might like to give it a go.
Now, now. Is it Rust -- or Go?
[SCNR]
--
t
Hi,
I concur with others that it sounds like you simply don't have sudo
installed.
As an aside, sudo-rs is packaged as of Debian 13 (trixie, currently
testing) and I've been using it for a week now without complaints. sudo
fans might like to give it a go.
It replicates the functionality and conf
Lee Winter writes:
> [A1] is that netinstall left /etc/sudoers missing and /etc/sudoers.d/README
> empty -- there are no users at all. But that
> README file contains a strong recommendation for using visudo, which no
> longer exists.
visudo is included in the sudo package. I'd expect you have
On Thu, Jul 10, 2025 at 07:13:48AM -0400, Lee Winter wrote:
> Got a dell 5400 workstation configured fully (8 cores, 32gb RAM, 160gb fast
> disk & 1.0tb slow disk) and I netinstalled debian Bookworm 12.10.0 on it.
> I also got the 20 DVDs with 92.5gb of Source packages. The machine seems
> OK, but
On Jul 10, 2025, Lee Winter wrote:
> Got a dell 5400 workstation configured fully (8 cores, 32gb RAM, 160gb
> fast disk & 1.0tb slow disk) and I netinstalled debian Bookworm
> 12.10.0 on it. I also got the 20 DVDs with 92.5gb of Source packages.
> The machine seems OK, but I am finding some [probl
On Thu, Jul 10, 2025 at 07:13:48 -0400, Lee Winter wrote:
> [A1] is that netinstall left /etc/sudoers missing and /etc/sudoers.d/README
> empty -- there are no users at all. But that README file contains a strong
> recommendation for using visudo, which no longer exists.
>
> [A2] is that visudo is
Got a dell 5400 workstation configured fully (8 cores, 32gb RAM, 160gb fast
disk & 1.0tb slow disk) and I netinstalled debian Bookworm 12.10.0 on it.
I also got the 20 DVDs with 92.5gb of Source packages. The machine seems
OK, but I am finding some [problem]s.
[A1] is that netinstall left /etc/s
On Mon, Jun 30, 2025 at 9:14 AM David Kennedy wrote:
>
> I was informed on the Debian Subreddit that this is where I should report an
> issue so just adding my post here too.
No, that advice is wrong.
Debian's Bug Tracking system is discussed at
<https://www.debian.org/
On Monday, 23-09-2024 at 19:48 newbie...@gmx.de wrote:
>
> hello friends,
>
> I tried but found it too confusing to find where to report bugs for debian
> :-( .
What GUI are you using? (e.g. Gnome, KDE, Xfec, etc ?)
Wayland or X11 ?
What is the model number of monito
hello friends,
I tried but found it too confusing to find where to report bugs for debian :-(
.
I see an issues in ver. 12.6.0 started from the live image:
Scaling the desktop by Settings - Display - General - Scale works
counter-intuitive, setting it to 2x reduces everything on
Hi,
a while ago I reported a bug against the kernel (Bug#1070717). But the bug
isn't limited to that kernel version and not even to the Debian kernel. The
same even happens when I e.g. compile Linux 9.3 from sources, using the config
from Debian's 6.6.15 - the latest version I tried that didn'
On Fri 01/03/2024 at 05:30, Jeffrey Walton wrote:
> On Fri, Mar 1, 2024 at 12:22 AM Gareth Evans wrote:
>>
>> I'm subscribed to debian-devel for entertainment purposes and see regular
>> wishlist "bug" reports, eg.
>>
>> https://lists.debian.org/debian-devel/2024/02/msg00321.html
>>
>> Can anyon
On Fri, Mar 1, 2024 at 12:22 AM Gareth Evans wrote:
>
> I'm subscribed to debian-devel for entertainment purposes and see regular
> wishlist "bug" reports, eg.
>
> https://lists.debian.org/debian-devel/2024/02/msg00321.html
>
> Can anyone advise of the appropriate way for non-developers to
> req
> On 1 Mar 2024, at 02:29, John Hasler wrote:
>
> https://wiki.debian.org/RFP
> --
> John Hasler
> j...@sugarbit.com
> Elmwood, WI USA
Excellent thanks
G
https://wiki.debian.org/RFP
--
John Hasler
j...@sugarbit.com
Elmwood, WI USA
I'm subscribed to debian-devel for entertainment purposes and see regular
wishlist "bug" reports, eg.
https://lists.debian.org/debian-devel/2024/02/msg00321.html
Can anyone advise of the appropriate way for non-developers to request/suggest
inclusion of packages?
Freenginx doesn't seem to be i
On Sun, 19 Nov 2023 08:56:11 +0100
dub...@grey-panther.net wrote:
> I didn't get an email reply and the reportbug script said something
> about the email being sent from "localhost" (since this is a LiveCD,
> email accounts are not properly set up). Hence me suspecting that the
> email never went
he cdimage.debian.org
> > meta-package, as described at https://www.debian.org/Bugs/Reporting,
> > however my bug doesn't show up in the bugtracker, even though it has
> > been several days now since I submitted it.
>
> Did you get an email response? If so, have you visit
On Sat, 18 Nov 2023 22:07:46 +0100
dub...@grey-panther.net wrote:
> Anyway, I ran the reportbug program with the cdimage.debian.org
> meta-package, as described at https://www.debian.org/Bugs/Reporting,
> however my bug doesn't show up in the bugtracker, even though it has
> been
Anyway, I ran the reportbug program with the cdimage.debian.org
meta-package, as described at https://www.debian.org/Bugs/Reporting,
however my bug doesn't show up in the bugtracker, even though it has been
several days now since I submitted it.
Does anybody know if reporting a bug from the li
On Thu 08 Sep 2022 at 10:02:15 +1000, David wrote:
> On Thu, 8 Sept 2022 at 03:14, Brian wrote:
> > On Wed 07 Sep 2022 at 15:48:35 +0100, Brad Rogers wrote:
> > > On Wed, 07 Sep 2022 12:39:23 + "jindam, vani"
> > > wrote:
>
> > Reports submitted from a specicic address may be viewed with
>
On Thu, 8 Sept 2022 at 03:14, Brian wrote:
> On Wed 07 Sep 2022 at 15:48:35 +0100, Brad Rogers wrote:
> > On Wed, 07 Sep 2022 12:39:23 + "jindam, vani"
> > wrote:
> Reports submitted from a specicic address may be viewed with
>
>
> https://bugs.debian.org/cgi-bin/pkgreport.cgi/submitter=
On Wed, 7 Sep 2022 18:14:22 +0100
Brian wrote:
Hello Brian,
>Reports submitted from a specicic address may be viewed with
Good to know. Bookmarked for future reference. Thank you.
--
Regards _
/ ) "The blindingly obvious is never immediately apparent"
/ _)rad "Is i
On Wed 07 Sep 2022 at 15:48:35 +0100, Brad Rogers wrote:
> On Wed, 07 Sep 2022 12:39:23 +
> "jindam, vani" wrote:
>
> Hello vani,
>
> >luckily there were few bugs created
> >by me..
>
> Yeah, it will probably be a real PITA to find all thos
On Wed, 07 Sep 2022 12:39:23 +
"jindam, vani" wrote:
Hello vani,
>luckily there were few bugs created
>by me..
Yeah, it will probably be a real PITA to find all those bugs already
submitted by you.
At least from now on, you've got some sort of mechanism to monito
On 7 September 2022 7:51:29 AM UTC, Brad Rogers wrote:
>On Wed, 07 Sep 2022 07:09:46 +
>"jindam, vani" wrote:
>
>Hello vani,
>
>>is it possible to view changes made
>>on bugs submitted by me using rss.
>
>AFAIAA, no. However, you *can* 's
On 2022-09-07 at 03:37, to...@tuxteam.de wrote:
> On Wed, Sep 07, 2022 at 07:09:46AM +, jindam, vani wrote:
>
>> hello debian users,
>>
>> is it possible to view changes made
>> on bugs submitted by me using rss. perhaps,
>> a moreinfo needed tag of a bu
On Wed, 07 Sep 2022 07:09:46 +
"jindam, vani" wrote:
Hello vani,
>is it possible to view changes made
>on bugs submitted by me using rss.
AFAIAA, no. However, you *can* 'subscribe' to the bug on bugs.debian
in much the same way you can subscribe to a mailing
On Wed, Sep 07, 2022 at 07:09:46AM +, jindam, vani wrote:
> hello debian users,
>
> is it possible to view changes made
> on bugs submitted by me using rss. perhaps,
> a moreinfo needed tag of a bug submitted
> by me didnt received through email.
>
> i am talking
hello debian users,
is it possible to view changes made
on bugs submitted by me using rss. perhaps,
a moreinfo needed tag of a bug submitted
by me didnt received through email.
i am talking about bugs submitted on
bugs.debian.org
regards,
jindam, vani
On Sun, Aug 21, 2022 at 10:06:08AM +0200, Oliver Schoede wrote:
> On Sat, 20 Aug 2022 13:26:14 +0100
> Brian wrote:
>
> >Reasons for the perceived "ignored" status might be:
[...]
> No, these are (more or less reasonable) grounds for not getting *to
> work* on some potential issue, and that is w
On Sat, 20 Aug 2022 13:26:14 +0100
Brian wrote:
>Reasons for the perceived "ignored" status might be:
>
> * The maintainer judges that the bug affects very few users.
> * The maintainer does not have the resources to deal with the bug.
> * A solution is already in hand and awaiting upload to unst
On Sat, Aug 20, 2022 at 04:20:21PM -0400, Chuck Zmudzinski wrote:
> On 8/20/2022 2:06 PM, Stefan Monnier wrote:
[...]
> > But note that *you* can help, by taking on some of the work, looking for
> > bugs that haven't gotten an answer yet and trying to address them.
>
&g
On 8/20/22 4:28 PM, Stefan Monnier wrote:
> Chuck Zmudzinski [2022-08-20 16:20:21] wrote:
> > That's a fair point. It may not be so easy for me to work on a bug that
> > does not affect
> > my systems, but I am willing to help with bugs important to the Debian
&
u filed a bug report about a problem you
> perceived in macOS, Windows, other your usual shrink wrapped software?
> Has it always been fixed promptly?
>
> If you want your bugs to be fixed, you generally need resort to some
> kind of support contract, which you can get for Fre
gt;> Usually upstream projects want and expect users to report bugs to
> >> the distro, not to the upstream project, for many good reasons that I
> >> need not explain here.
> >
> >You would have to explain it for my benefit because I am not familiar
> >with that p
justify
> > to their bosses that the 1400 dollars "spent" on this are coming
> > back in some way.
>
> There are plenty of "volunteers" for free software projects that also
> work, as you say, in the "belly of big corps." Are you suggesting these
>
On 8/20/2022 1:25 AM, to...@tuxteam.de wrote:
> On Fri, Aug 19, 2022 at 05:06:38PM -0400, Chuck Zmudzinski wrote:
> > On 8/19/2022 4:44 PM, piorunz wrote:
> > > On 19/08/2022 18:57, Chuck Zmudzinski wrote:
> > >
> > > > I have noticed that some
On Sat, 20 Aug 2022 15:22:27 +0100
Brian wrote:
Hello Brian,
>On Sat 20 Aug 2022 at 09:06:54 -0400, Chuck Zmudzinski wrote:
>> On 8/20/2022 1:25 AM, to...@tuxteam.de wrote:
>> Usually upstream projects want and expect users to report bugs to
>> the distro, not to the
On Sat, Aug 20, 2022 at 03:22:27PM +0100, Brian wrote:
> On Sat 20 Aug 2022 at 09:06:54 -0400, Chuck Zmudzinski wrote:
> > Usually upstream projects want and expect users to report bugs to
> > the distro, not to the upstream project, for many good reasons that I
> > need not e
the best possible thing.
> Usually upstream projects want and expect users to report bugs to
> the distro, not to the upstream project, for many good reasons that I
> need not explain here.
You would have to explain it for my benefit because I am not familiar
with that procedure.
>
On 8/20/2022 1:25 AM, to...@tuxteam.de wrote:
> On Fri, Aug 19, 2022 at 05:06:38PM -0400, Chuck Zmudzinski wrote:
> > On 8/19/2022 4:44 PM, piorunz wrote:
> > > On 19/08/2022 18:57, Chuck Zmudzinski wrote:
> > >
> > > > I have noticed that some
On Fri 19 Aug 2022 at 13:57:29 -0400, Chuck Zmudzinski wrote:
> Hello,
>
> I have noticed that some Debian bugs are ignored for a long time,
> sometimes even when the person who submitted the bug offered a patch.
> The Debian developers/maintainers sometimes don't even r
it. That's fine, but...
If Debian developers/maintainers actively refuse to fix some bugs that
inevitably arise
by ignoring them, why would anyone depend on Debian software for anything
important?
Did you not read Debian disclaimer when you log in?
"The programs included with the Deb
volunteers
> will never be as stable and secure as software that is written by
> people who are paid by the hour. That is, Debian software can *never*
> be as stable and secure as software that is written and maintained by
> people who are paid by the hour.
Too much generalizing.
On Fri, Aug 19, 2022 at 05:06:38PM -0400, Chuck Zmudzinski wrote:
> On 8/19/2022 4:44 PM, piorunz wrote:
> > On 19/08/2022 18:57, Chuck Zmudzinski wrote:
> >
> > > I have noticed that some Debian bugs are ignored for a long time [...]
> >
> > Hi Chuck,
> >
On 8/19/2022 9:18 PM, Andy Smith wrote:
> Hi Chuck,
>
> On Fri, Aug 19, 2022 at 08:20:21PM -0400, Chuck Zmudzinski wrote:
> > On 8/19/2022 6:59 PM, Andy Smith wrote:
> > > Volunteers cannot be forced to do work, else they are not
> > > volunteers.
> >
> > The fact that Debian is created by volunte
Chuck Zmudzinski writes:
> On 8/19/2022 6:59 PM, Andy Smith wrote:
>> Hello,
>>
>> On Fri, Aug 19, 2022 at 05:06:38PM -0400, Chuck Zmudzinski wrote:
>> > On 8/19/2022 4:44 PM, piorunz wrote:
>> > > On 19/08/2022 18:57, Chuck Zmudzinski wrote:
>>
Hi Chuck,
On Fri, Aug 19, 2022 at 08:20:21PM -0400, Chuck Zmudzinski wrote:
> On 8/19/2022 6:59 PM, Andy Smith wrote:
> > Volunteers cannot be forced to do work, else they are not
> > volunteers.
>
> The fact that Debian is created by volunteers and therefore the chances are
> high that users mig
On 8/19/2022 6:59 PM, Andy Smith wrote:
> Hello,
>
> On Fri, Aug 19, 2022 at 05:06:38PM -0400, Chuck Zmudzinski wrote:
> > On 8/19/2022 4:44 PM, piorunz wrote:
> > > On 19/08/2022 18:57, Chuck Zmudzinski wrote:
> > > > I have noticed that some Deb
Hello,
On Fri, Aug 19, 2022 at 05:06:38PM -0400, Chuck Zmudzinski wrote:
> On 8/19/2022 4:44 PM, piorunz wrote:
> > On 19/08/2022 18:57, Chuck Zmudzinski wrote:
> > > I have noticed that some Debian bugs are ignored for a long time,
> > > sometimes even when the p
:
> >
> > On 8/19/2022 4:44 PM, piorunz wrote:
> > > On 19/08/2022 18:57, Chuck Zmudzinski wrote:
> > >
> > > > I have noticed that some Debian bugs are ignored for a long
> time, sometimes even when the person who sub
On 8/19/2022 4:44 PM, piorunz wrote:
> On 19/08/2022 18:57, Chuck Zmudzinski wrote:
>
> > I have noticed that some Debian bugs are ignored for a long time, sometimes
> > even when the person who submitted the bug offered a patch. The Debian
> > developers/maintainers so
On 19/08/2022 18:57, Chuck Zmudzinski wrote:
I have noticed that some Debian bugs are ignored for a long time, sometimes
even when the person who submitted the bug offered a patch. The Debian
developers/maintainers sometimes don't even reply and therefore never explain
why the proposed
Hello,
I have noticed that some Debian bugs are ignored for a long time, sometimes
even when the person who submitted the bug offered a patch. The Debian
developers/maintainers sometimes don't even reply and therefore never explain
why the proposed patch cannot be applied. Why is that the
On 2022-07-23 09:29:33 -0400, Greg Wooledge wrote:
> Sometimes, the only way to fix security bugs is to use a newer upstream
> version. The Debian teams try hard to avoid it, but it has happened
> before, and it will happen again.
Yes, they did that with firefox in the past, wit
bian.org/news/1345038/accepted-nvidia-graphics-drivers-47012906-6deb11u1bpo101-source-amd64-into-buster-backports-backports-policy-buster-backports/
> closes 24 bugs and fixes 6 CVEs.
>
> Obviously this was not a cautious detail fix by a concise patch but
> rather a switch to a new up
Hi,
i wrote:
> > Well, "stable" means old software with old bugs. Those who want the new
> > bugs, which are introduced by fixing the old ones, have to run something
> > else.
Alexander V. Makartsev wrote:
> Then why "nvidia-driver" in Stable was switched
On 23.07.2022 12:39, Thomas Schmitt wrote:
Hi,
Surely "Closes:" is very convenient, but wouldn't you agree that this
puts the users of Stable at a disadvantage?
Well, "stable" means old software with old bugs. Those who want the new
bugs, which are introduced by fix
Hi,
> Surely "Closes:" is very convenient, but wouldn't you agree that this
> puts the users of Stable at a disadvantage?
Well, "stable" means old software with old bugs. Those who want the new
bugs, which are introduced by fixing the old ones, have to run som
On Sat, 2022-07-23 at 09:04 +0200, Harald Dunkel wrote:
> Hi folks,
>
> what is Debian's policy wrt bugs reported for a package in Stable (e.g.
> some daemon eating up 100% CPU)? Looking at the "Closes:" feature for
> debian/changelog I have the impression that a f
Hi folks,
what is Debian's policy wrt bugs reported for a package in Stable (e.g.
some daemon eating up 100% CPU)? Looking at the "Closes:" feature for
debian/changelog I have the impression that a fix in Unstable is seen
to be sufficient "to get rid" of the bug report.
On Thu, Jul 21, 2022 at 02:16:40PM -0500, kjohn...@eclypse.org wrote:
> I would like to see fixed bugs for the mailman3 package, and related packages.
Start by going to the package's bug page:
<http://bugs.debian.org/mailman3>
At the bottom of the page, there's a form
How do I see fixed bugs for a package at bugs.debian.org? I can find open bugs
from https://www.debian.org/Bugs/, but maybe something that has been fixed
would give me insight.
I would like to see fixed bugs for the mailman3 package, and related packages.
I am trying to migrate from mailman2
On Fri 10 Jun 2022 at 19:38:22 +, Jonathan Wiebe wrote:
> I need a pointer as to how to file a bug against the Debian website.
File against www.debian.org.
--
Brian.
I need a pointer as to how to file a bug against the Debian website.
The following webpages all contain the text:
The second set of tags indicate what releases a bug applies to: O for oldstable
(jessie), S for stable (stretch), T for testing (buster), U for unstable (sid)
or E for experimental.
On Ma, 02 feb 21, 14:23:05, kamaraju kusumanchi wrote:
> Is there a way to get the number of bugs filed against a package that
> affect a specific version of a package? The closest I was able to
> achieve is
>
> % querybts -u text -b libc6-dev 2> /dev/null | wc -l
> 38
>
Is there a way to get the number of bugs filed against a package that
affect a specific version of a package? The closest I was able to
achieve is
% querybts -u text -b libc6-dev 2> /dev/null | wc -l
38
which shows all bugs filed on libc6-dev. But it does not, for example,
show me the number
Hello,
Will trying to install OpenQA on Debian, I discovered a bugs opened on
bugs.debian.org.
I tried to make the driver, it's seem to work but i've been stuck, how i
can help DD on this paquages, it's been 5 years old now.
Thanks
Why is my account is been bugs
My
Hello,
On Sun, Jun 28, 2020 at 01:42:02PM +0200, Daniel Widenfalk wrote:
> I would very much appreciate some quick pointers on how to properly report
> this so that I don't have to dig up my posts to the xen users mailing list
> to figure out something I already should know.
Xen is a pretty fring
Hi,
Four years ago I ran into two issues with the xen support in Debian - at
that time I forgot to report these issues back to Debian. Now, when
setting up a new machine I ran into the second of these issues (and it
turned out that the first one was still there).
Scenario: An Amd 3700X CPU o
backports and everything is
> rock-solid.
>
> But I am afraid that we have deviated from the original topic. If I
> understood Carl correctly - he was expressing his pain because of
> bureaucratic scrutiny of filing bugs to stable that brings absolutely no
> results.
"
mentioned - backports should be the first option to try
if you run stable. I run a few servers stable + backports and everything is
rock-solid.
But I am afraid that we have deviated from the original topic. If I
understood Carl correctly - he was expressing his pain because of
bureaucrati
On Du, 19 apr 20, 13:28:57, Ihor Antonov wrote:
>
> Reporting from Debian Sid, everything is quite stable. I do run ZFS on root
> and make snapshots prior to big upgrades as a pre-caution, but so far
> I did not have a reason to revert anything.
It's just a matter of time. Even if Debian does
quest from reportbug to try a
newer version.
Why is reportbug even in Stable? Why not just replace it with a script that
says "Sorry, bugs in Stable are never fixed. Try Testing." Seriously, that's
literally the Debian policy, that only security fixes are done in Stable.
gt; fiddling with pointlessly arcane configuration files that are sort of
> documented
> if you squint.
>
> (Yes, the pun on "bug" is deliberate.)
>
> Why is reportbug even in Stable? Why not just replace it with a script that
> says "Sorry, bugs in Stable are nev
ng you mean the standard request from reportbug to try a
> newer version.
>
>> Why is reportbug even in Stable? Why not just replace it with a script
>> that
>> says "Sorry, bugs in Stable are never fixed. Try Testing." Seriously,
>> that's
>> lit
>
> By? I'm guessing you mean the standard request from reportbug to try a
> newer version.
>
> > Why is reportbug even in Stable? Why not just replace it with a script
> > that
> > says "Sorry, bugs in Stable are never fixed. Try Testing." Seriously,
&g
On Sun, 2020-04-19 at 10:27 -0400, Carl Fink wrote:
> On Sun, Apr 19, 2020 at 09:51:02AM -0400, Jim Popovitch wrote:
>
> > What applications do you feel aren't up-to-date enough for your liking?
> > I'm genuinely curious.
>
> Mr. Heskett's comments made me want to tell him how to lower the CPU us
On Sun, 19 Apr 2020 09:51:02 -0400
Jim Popovitch wrote:
> On Sun, 2020-04-19 at 09:43 -0400, Carl Fink wrote:
> > Why is reportbug even in Stable? Why not just replace it with a script that
> > says "Sorry, bugs in Stable are never fixed. Try Testing." Seriously, that&#
On Sun, Apr 19, 2020 at 09:51:02AM -0400, Jim Popovitch wrote:
> What applications do you feel aren't up-to-date enough for your liking?
> I'm genuinely curious.
Mr. Heskett's comments made me want to tell him how to lower the CPU usage
of BOINC. However, boinc-manager in Stable, at least on my s
er version.
> Why is reportbug even in Stable? Why not just replace it with a script that
> says "Sorry, bugs in Stable are never fixed. Try Testing." Seriously, that's
> literally the Debian policy, that only security fixes are done in Stable.
Actually bugs of severity &
On Sun, 2020-04-19 at 09:43 -0400, Carl Fink wrote:
> Why is reportbug even in Stable? Why not just replace it with a script that
> says "Sorry, bugs in Stable are never fixed. Try Testing." Seriously, that's
> literally the Debian policy, that only security fixes are done
ed
if you squint.
(Yes, the pun on "bug" is deliberate.)
Why is reportbug even in Stable? Why not just replace it with a script that
says "Sorry, bugs in Stable are never fixed. Try Testing." Seriously, that's
literally the Debian policy, that only security fixes are done i
tly clear for me :)
>
> Reviewing is the issue. It needs a real person to read the mail, make
> a judgement and do it. Half-a-dozen dedicated volunteers would probably
> be enough to keep the BTS clean of spam.
AFAICT the number of volunteers has been zero for many years. I have
reported dozens if not hundreds of spam-infested bugs, and never saw the
spam actually removed.
So reporting a bug as spam does not do any harm, but it is a minor waste
of time in my experience.
Cheers,
Sven
On Sun 17 Nov 2019 at 21:36:11 +0100, Linux-Fan wrote:
> Brian writes:
>
> > On Sun 17 Nov 2019 at 21:01:16 +0100, Linux-Fan wrote:
>
> [...]
>
> > > Verify report for bug 692728
> > > Yes, report that bug 692728 has spam
> > >
> > > Now I am not sure (maybe it's a language thing): Is it OK
Brian writes:
On Sun 17 Nov 2019 at 21:01:16 +0100, Linux-Fan wrote:
[...]
>Verify report for bug 692728
>Yes, report that bug 692728 has spam
>
> Now I am not sure (maybe it's a language thing): Is it OK to continue
> eventhough most of the bug is quite important discussion and only
On Sun 17 Nov 2019 at 21:01:16 +0100, Linux-Fan wrote:
> I just came across the following bug:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692728
> It is really a shame that the program is no longer licensed freely*** :(
>
> If one scrolls down to the last message of the bug, it seems to
Hello fellow list members,
I just came across the following bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692728
It is really a shame that the program is no longer licensed freely*** :(
If one scrolls down to the last message of the bug, it seems to be spam and
a dangerous one at that w
I would appreciate it since y’all received it
Sent from my iPhone
On Wed 22 May 2019 at 13:32:09 (-0400), nico.schloe...@gmail.com wrote:
> > Try avoid the GUI mode of reportbug.
>
> How do I do this? `reportbug -h` doesn't say anything about it.
Supply 'text' to -u.
$ reportbug -h | grep -i interface
-u INTERFACE, --interface=INTERFACE, --ui=INTERFACE
Quoting nico.schloe...@gmail.com (2019-05-22 19:32:09)
> Thank you too for the quick reply.
>
> > Try avoid the GUI mode of reportbug.
>
> How do I do this? `reportbug -h` doesn't say anything about it.
On my Debian system `man reportbug` mentions "gtk" in relation to a "-u"
option - if yours d
Okay, I couldn't figure out how to change the the order of paths in
`sys.path`, but I went ahead and removed
```
pip3 uninstall pysimplesoap
```
from `~/.local/`. I have no idea what was the difference between my
locally installed version and the system version but reportbug works
now.
Thanks ever
On Wed, 22 May 2019 19:04:52 +0200
Nico Schlömer wrote:
> Thanks Michael for the quick response!
> ```
> python3 -c "import sys; print(sys.path)"
> ```
> gives
> ```
> ['', '/usr/lib/python37.zip', '/usr/lib/python3.7',
> '/usr/lib/python3.7/lib-dynload',
> '/home/nschloe/.local/lib/python3.7/sit
d"
Your scepticism prompted me to check again and indeed, I had overlooked a
failure message from debian. Apparently, there was something wrong with my
"pseudo headers". I'll read the instructions [1] again and try once more.
Cheers,
Nico
[1] https://www.debian.org/Bugs/Reportin
Hi Nico,
Quoting Nico Schlömer (2019-05-22 18:25:16)
> Phew, I find it quite difficult to report bugs in Debian.
[ meta complaints snipped ]
> When launching
> ```
> reportbug -B debian
> ```
> (running Ubuntu 19.04) and after two, three clicks I'm getting
Thanks for
most recent call last):
> > File "/usr/lib/python3/dist-packages/reportbug/ui/gtk_ui.py", line
> > 1049, in sync_pre_operation
> > http_proxy=http_proxy, archived=archived, source=source)
> > File "/usr/lib/python3/dist-packages/reportbug/debbugs.
1 - 100 of 583 matches
Mail list logo
