Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
On Tue 08 Nov 2011 at 22:48:28 +0200, Andrei Popescu wrote: > I can only say "Wow!" But you said it so charmingly. :-) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2008235638.GD2852@desktop
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
On Ma, 08 nov 11, 19:13:03, Brian wrote: > > Instead of penalising many 1000s of legitimate users the network > administrators could remove the connectivity of the offenders. Why don't > they? My own ISP conducts regular sweeps for open relays and has an > abuse department which takes rigorous action to prevent its network > being a source of UBE. I can only say "Wow!" Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
On Tue 08 Nov 2011 at 10:57:27 -0700, Bob Proulx wrote: > Good information. Thanks for sharing it. > > A possible downside to that setting is that your host will try to > connect directly to the reportbug.debian.org host on smtp port 25. By > itself that is fine. But many networks today block port 25 as an > anti-spam from local virus infected MS-PCs measure. On those networks > such a setting will be blocked from connecting directly. Blocking > port 25 outbound is becoming more and more common. Instead of penalising many 1000s of legitimate users the network administrators could remove the connectivity of the offenders. Why don't they? My own ISP conducts regular sweeps for open relays and has an abuse department which takes rigorous action to prevent its network being a source of UBE. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2008191303.GB2852@desktop
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
Andrei Popescu wrote: > On Lu, 10 oct 11, 18:38:33, Bob Proulx wrote: > > 3. Reportbug sends the bug report bug using /usr/sbin/sendmail as the > >MTA. If that doesn't work then reportbug (and other commands too) > >will have problems. I have no workaround to /usr/sbin/sendmail not > >working. That simply must work for a healthy system. If that is > >the problem then solve that problem first. > > Run 'reportbug --configure' and read carefully the prompts about an MTA. > reportbug can send reports without any (potentially (mis)configured) > local or remote SMTP server. The relevant configuration in .reportbugrc > is: > > smtphost reportbug.debian.org Good information. Thanks for sharing it. A possible downside to that setting is that your host will try to connect directly to the reportbug.debian.org host on smtp port 25. By itself that is fine. But many networks today block port 25 as an anti-spam from local virus infected MS-PCs measure. On those networks such a setting will be blocked from connecting directly. Blocking port 25 outbound is becoming more and more common. Bob signature.asc Description: Digital signature
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
On Lu, 10 oct 11, 18:38:33, Bob Proulx wrote: > > 3. Reportbug sends the bug report bug using /usr/sbin/sendmail as the >MTA. If that doesn't work then reportbug (and other commands too) >will have problems. I have no workaround to /usr/sbin/sendmail not >working. That simply must work for a healthy system. If that is >the problem then solve that problem first. Run 'reportbug --configure' and read carefully the prompts about an MTA. reportbug can send reports without any (potentially (mis)configured) local or remote SMTP server. The relevant configuration in .reportbugrc is: smtphost reportbug.debian.org Hope this helps, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
On Thu, 13 Oct 2011 20:21:30 -0600, Bob Proulx wrote: I will try to be very brief to avoid getting you extenuated ;-) > Camaleón wrote: (about Flash Player support in ARM platform...) >> (although it seems that ARM already supports Flash Player¹) > > I did not know that ARM now had closed source proprietary binary blobs > for it. As you can see ARM truly is a first class architecture. :-) Glad you finally feel like a first class citizen :-) (here comes more about the ability of browsers to send computer information via http and thus exposing a possible hole for threats... omitted because is not relevant at all for the main issue of this thread) >> But this is not about "Debian" but "bug reporting" for Debian. >> >> And reporting bugs can happen on any platform. You can be running >> Debian but having the system at a completely unbootable stage nd you >> need to report a bug in a windows/macos/solaris machine... what to do >> then if reportbug is not available under those systems? Manually gather >> the required data and write an e-mail? > > Yes! That is exactly correct. You are expected to write an email. (...) And _I do know_ how to do that and _I do know_ about that's a possibility. (this was exposed by me in my first post on this thread) But this is no about _me_ (I _do know_ how to do these things and to do) but all of the users that come to Debian and have to deal with the current system for reporting bugs which translates into reportbug or e- mail. Reportbug is nice but it has to be installed on the system you are reporting against and manually composing a preformatted e-mail to report a bug is not an easy task. If we want users do not report bugs, failures or wishes I'd say we are on the right track: the current system is discouraging :-) (about using a centralized web-based bugzilla-alike system for bug tracking) > I reject the argument that whatever is most popular, whatever is used by > the most people, is the best method just because it has the most users > using it. I did not say that, it's you that interpreted in such a way. I think that a bug reporting system that works for other "big" open source projects (like kernel.org, gnome, kde, mozilla, SuSE, RedHat/ Fedora, Ubuntu, Archlinux...) can be also of our interest. And I don't want to put the focus specially in Bugzilla but any other tracking system that is centralized and accesible via http (i.e., track, mantis, fossil or even Launchpad that seems to integrate well with our debbug system). > And since Debian isn't the most popular operating system on the planet I > dare say that all of us Debian users have also rejected that too. > Otherwise we would not be running Debian but would instead be running a > more popular operating system. I am not aware of any poll asking debian users for their preferred bug reporting tools and that would be a great idea >:-) (mixed stuff...) >> > To be clear I have never opposed having a web interface to submit >> > bugs to the BTS. I however think the best part of the BTS is the >> > ability to use email to interface to it. Email is so simple and >> > pervasive that I can't see ever wanting to use any other method. >> >> Maybe you did not read well what I said before. > > I was reacting to and disagreeing with the premise that a web form can > run processes that access the local filesystem. (...) I did not say a word about "web forms" but the possibilities it provides the use of http protocol by any means. > Along the way there was discussion about reportbug crashing. I believe > the standard reportbug to be rock solid. You believe it to be terrible > unreliable and buggy. (...) Hey, stop here. I say it crashes very often (it does, and that's not something I have dreamed, there are bug reports on crashes and in this list you have seen posts stating so), don't put in my mouth something that I did not say. > Through the discussion it was revealed that > invoking reportbug through the GNOME menu system starts it using a > graphical GUI system. That graphical GUI was previously unknown to me. It seems there many things that you were not aware they existed (first, the ARM support for Flash player and now the GUI option for reportbug). That's fine but you should not make claims for things that you have to even tried! ;-) > I have only ever launched it from a shell prompt. Who would have > thought that someone would have written a GUI for such a simple tool? Who...? Debian devels? ;-) And why having a GUI to manage an application is something bad? If you are on a X session, that's the expected. > I find that unfathomable. I daresay that you believe the GUI to be the > standard interface to reportbug and probably the only way you had ever > seen it. Apparently that interface is unreliable. I believe the text > interface to be the standard interface. Apparently that interface is > reliable. But again, this is not about _you_ nor _me_ as we
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
Camaleón wrote: > Bob Proulx wrote: > > Yes, an ARM machine. And I picked that one because there is no Adobe > > Flash for ARM. > > (although it seems that ARM already supports Flash Player¹) I did not know that ARM now had closed source proprietary binary blobs for it. As you can see ARM truly is a first class architecture. :-) > Again, I selected Flash player as an example of what can be done through > a web browser. HTML5 was another example I used. If you don't like this > specific example (although it seems that ARM already supports Flash > Player¹), you can rename "flash player" by "java" or whatever plugin you > prefer. Regardless of what you substitute in there those all operate by design in a sandbox with limited access to the underlying host. Otherwise it creates a security vulnerability. And of course when the sandbox is penetrated due to a bug then an actual vulnerability exists and must be fixed. > > I am talking about "Debian". This is a Debian mailing list. Debian > > supports many architectures and not just 32-bit x86. Are we talking > > about "you" specifically here running a 32-bit x86 architecture and able > > to run Adobe Flash? :-) > > But this is not about "Debian" but "bug reporting" for Debian. > > And reporting bugs can happen on any platform. You can be running Debian > but having the system at a completely unbootable stage nd you need to > report a bug in a windows/macos/solaris machine... what to do then if > reportbug is not available under those systems? Manually gather the > required data and write an e-mail? Yes! That is exactly correct. You are expected to write an email. http://www.debian.org/Bugs/Reporting Sending the bug report via e-mail You can report bugs in Debian by sending an e-mail to sub...@bugs.debian.org with a special format described below. reportbug (see above) will properly format the e-mails for you; please use it! As seen by the volume of email on this mailing list, sending an email is very easy making this form of bug reporting very accessible. > I'd say "interoperability" is the key for a Bugzilla-alike reporting > system. Interoperability and "standarization" between projects because > Bugzilla is a very well-known platform in other open source projects so > for users who were already used to that system, the learning curve will > be "zero" when they have to report in Debian. I reject the argument that whatever is most popular, whatever is used by the most people, is the best method just because it has the most users using it. And since Debian isn't the most popular operating system on the planet I dare say that all of us Debian users have also rejected that too. Otherwise we would not be running Debian but would instead be running a more popular operating system. > > I am talking about mainstream Debian systems. Debian has been called > > the Universal Operating System for good reason. It runs on many > > different architectures. Here is the official list. > > > > http://www.debian.org/ports/ > > > > Debian is all about free(dom) software and the Social Contract and the > > DFSG (Debian Free Software Guidelines) reflect this. If you have the > > source code then you are not limited to a proprietary blob limiting you > > to a specific architecture. If you have the source code then you are > > free to run on whatever architecture you have available. This is a core > > point of Debian and one that makes it "Outstanding". :-) > > Good. You have given me more arguments... Do you know something more > open, universal and flexible than the web and its protocols? Email? :-) > In what way is Bugzilla reporting tool -or similar applications- > limiting any of the above, being also "open source"? ;-) At that point in the discussion I was referencing your referencing of Adobe Flash which is a closed source proprietary binary blob and that it is not available for every architecture. Sorry for not making that clear. Adobe Flash is not free software neither is it open source software, does not meet the DFSG, and cannot be part of Debian. > >> To be sincere, I don't care about flash player very much, just put it > >> as an example of what can be done with a small plugin and a browser. > > > > "Small" plugin? Maybe. (At 134K I think that is quite large.) But it > > certainly has been a big problem for a long time. In any case it is a > > good example of a bad example. > > It's very small for what it provides. It's about ~20 MiB of size in my > system, though. Did I say 134K? My bad. I slipped a finger and looked at the Java plugin. The Adobe Flash plugin is 12M on an x86 system. That is pretty large. 12M /usr/lib/flashplugin-nonfree/libflashplayer.so > And for the "bad example", well, that's your personal opinion. I was not > referring about its quality nor its code, but I find is a perfect example > for an addon and its current capabilities. One thing is that we don
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
On Wed, 12 Oct 2011 22:07:04 -0600, Bob Proulx wrote: > Camaleón wrote: >> Bob Proulx wrote: >> > Camaleón wrote: >> >> Besides, I'm sure you know that flash player plugin can contact you >> >> webcam and audio devices very easily. >> > >> > Is that true on an ARM based platform? Remember that Debian supports >> > a large number of architectures. AFAIK there is no Adobe Flash >> > available for ARM based systems. >> >> And what has ARM to do with this? Are you running an ARM based machine? >> Yes? Then good for you :-) But people running flash player on their >> systems are subject to that type of scannings. > > Yes, an ARM machine. And I picked that one because there is no Adobe > Flash for ARM. Again, I selected Flash player as an example of what can be done through a web browser. HTML5 was another example I used. If you don't like this specific example (although it seems that ARM already supports Flash Player¹), you can rename "flash player" by "java" or whatever plugin you prefer. >> > Is that true with Gnash (GNU Flash)? Gnash is the only flash player >> > on my main desktop (although other machines of mine have the Adobe >> > proprietary player). (Although I mentioned ARM above my main desktop >> > is amd64. I didn't want to be misleading here. But I do have ARM >> > based systems.) >> >> Good, but again, are we talking about "you" specifically or we are >> taking a more wide user case? > > I am talking about "Debian". This is a Debian mailing list. Debian > supports many architectures and not just 32-bit x86. Are we talking > about "you" specifically here running a 32-bit x86 architecture and able > to run Adobe Flash? :-) But this is not about "Debian" but "bug reporting" for Debian. And reporting bugs can happen on any platform. You can be running Debian but having the system at a completely unbootable stage nd you need to report a bug in a windows/macos/solaris machine... what to do then if reportbug is not available under those systems? Manually gather the required data and write an e-mail? I'd say "interoperability" is the key for a Bugzilla-alike reporting system. Interoperability and "standarization" between projects because Bugzilla is a very well-known platform in other open source projects so for users who were already used to that system, the learning curve will be "zero" when they have to report in Debian. >> I am telling you what happens right now with technology that is >> available in our systems, I can't speak for every concrete desktop >> there is on the earth as you can understand... > > I am talking about mainstream Debian systems. Debian has been called > the Universal Operating System for good reason. It runs on many > different architectures. Here is the official list. > > http://www.debian.org/ports/ > > Debian is all about free(dom) software and the Social Contract and the > DFSG (Debian Free Software Guidelines) reflect this. If you have the > source code then you are not limited to a proprietary blob limiting you > to a specific architecture. If you have the source code then you are > free to run on whatever architecture you have available. This is a core > point of Debian and one that makes it "Outstanding". :-) Good. You have given me more arguments... Do you know something more open, universal and flexible than the web and its protocols? In what way is Bugzilla reporting tool -or similar applications- limiting any of the above, being also "open source"? ;-) >> To be sincere, I don't care about flash player very much, just put it >> as an example of what can be done with a small plugin and a browser. > > "Small" plugin? Maybe. (At 134K I think that is quite large.) But it > certainly has been a big problem for a long time. In any case it is a > good example of a bad example. It's very small for what it provides. It's about ~20 MiB of size in my system, though. And for the "bad example", well, that's your personal opinion. I was not referring about its quality nor its code, but I find is a perfect example for an addon and its current capabilities. One thing is that we don't like Flash Player and another thing is neglecting its capabilities. >> Bugzilla (and related web based bug tracking systems) also provides >> wizards which guide the user to write the report. It's the same as >> reportbug, you can customize the level of help you want to receive and >> set that level as the default for the next time. > > To be clear I have never opposed having a web interface to submit bugs > to the BTS. I however think the best part of the BTS is the ability to > use email to interface to it. Email is so simple and pervasive that I > can't see ever wanting to use any other method. Maybe you did not read well what I said before. I wouldn't like to see reportbug dissapearing nor losing the possibility to send bug reports by e-mail , that would be terrible. What I said is I would like to have *an alternative* way for bug
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
Camaleón wrote: > Bob Proulx wrote: > > Camaleón wrote: > >> Besides, I'm sure you know that flash player plugin can contact you > >> webcam and audio devices very easily. > > > > Is that true on an ARM based platform? Remember that Debian supports a > > large number of architectures. AFAIK there is no Adobe Flash available > > for ARM based systems. > > And what has ARM to do with this? Are you running an ARM based machine? > Yes? Then good for you :-) But people running flash player on their > systems are subject to that type of scannings. Yes, an ARM machine. And I picked that one because there is no Adobe Flash for ARM. > > Is that true with Gnash (GNU Flash)? Gnash is the only flash player on > > my main desktop (although other machines of mine have the Adobe > > proprietary player). (Although I mentioned ARM above my main desktop is > > amd64. I didn't want to be misleading here. But I do have ARM based > > systems.) > > Good, but again, are we talking about "you" specifically or we are taking > a more wide user case? I am talking about "Debian". This is a Debian mailing list. Debian supports many architectures and not just 32-bit x86. Are we talking about "you" specifically here running a 32-bit x86 architecture and able to run Adobe Flash? :-) > I am telling you what happens right now with technology that is available > in our systems, I can't speak for every concrete desktop there is on the > earth as you can understand... I am talking about mainstream Debian systems. Debian has been called the Universal Operating System for good reason. It runs on many different architectures. Here is the official list. http://www.debian.org/ports/ Debian is all about free(dom) software and the Social Contract and the DFSG (Debian Free Software Guidelines) reflect this. If you have the source code then you are not limited to a proprietary blob limiting you to a specific architecture. If you have the source code then you are free to run on whatever architecture you have available. This is a core point of Debian and one that makes it "Outstanding". :-) > To be sincere, I don't care about flash player very much, just put it as > an example of what can be done with a small plugin and a browser. "Small" plugin? Maybe. (At 134K I think that is quite large.) But it certainly has been a big problem for a long time. In any case it is a good example of a bad example. > Bugzilla (and related web based bug tracking systems) also provides > wizards which guide the user to write the report. It's the same as > reportbug, you can customize the level of help you want to receive and > set that level as the default for the next time. To be clear I have never opposed having a web interface to submit bugs to the BTS. I however think the best part of the BTS is the ability to use email to interface to it. Email is so simple and pervasive that I can't see ever wanting to use any other method. > > But I disagree completely here that a web browser filling in a web form > > has access to the local system as it is intended to be impossible by > > design and security layers to run local programs across the local > > filesystem as a web form. Note that Javascript runs inside a security > > layer and is restricted from this access. > > Oh, come on, is not that hard. In the worst scenario, you can tell the > user to download a script with instructions to run it and then send the > output to a file to be uploaded with the report. I think that would be teaching users bad habits. Most users are not well versed on the details of verifying trust paths from scripts downloaded from the Internet. > That's all. It's possible, easy and convenient for the user that can run > the script when he/she wants and attach it to the bug later, when there > is Internet connection, for example. So... There could be a script on the web site. The user could download the script and run it. That script could be called something like "reportbug"? :-) > > Try moving it out of the way and running without local customization. > > > > $ mv ~/.reportbugrc reportbugrc.suspect > > $ reportbug -b somepackage > > I had to not only remove that config file several times but also set > "ncurses" GUI as the default to avoid perpetual crashes... Does that mean that when you were experiencing crashes you were using a graphical GUI interface? If so then that is not the default and must have been customized that way. If so then that explains the problem. I dare say that people like me who have never experienced a crash are using 'reportbug' in the default configuration and those that are complaining about it crashing have turned on some GUI interface. There appears to be one. I have never used it. It is not the default setting. I didn't even know it existed until a moment ago. Bob signature.asc Description: Digital signature
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
On Tue, 11 Oct 2011 16:37:17 + (UTC) Camaleón wrote: > On Tue, 11 Oct 2011 10:57:50 -0400, Celejar wrote: > > > On Tue, 11 Oct 2011 12:15:46 + (UTC) Camaleón > > wrote: > > > >> On Mon, 10 Oct 2011 17:50:10 -0600, Bob Proulx wrote: > >> > >> > Camaleón wrote: > >> >> Darac Marjal wrote: > > > > ... > > > >> >> And bugzilla does not tend to crash when writing bug reports >:-) > >> >> > >> >> In fact, I usually avoid using "reportbug" because of its high > >> >> instability (it's annoying having to re-do a full report several > >> >> times...) and finally send the report "manually" -by e-mail- which > >> >> is not a task for newcomers neither encourages people to write bug > >> >> reports ;-( > >> > > >> > I have never ever seen reportbug crash. > >> > >> You must be then a happy camper and the luckiest person in the hill. > > > > I can't recall the last time (if ever) that I had a reportbug crash > > (usually running uptodate Sid). > > It's okay that you have not experienced any error when running sid's > reportbug, but let people who indeed do have had express their > frustation :-) I have no problem with anyone reporting his or her experiences, and he or she should have no problem with me expressing mine ;) And I was correcting your implication that having no problems is extremely rare. Celejar -- foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111012101819.197a299a960ebb75fc3c8...@gmail.com
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
On Wed, 12 Oct 2011 14:12:30 +0100, Brian wrote: > On Wed 12 Oct 2011 at 10:30:53 +, Camaleón wrote: > >> On Tue, 11 Oct 2011 19:58:27 +0100, Brian wrote: >> >> > Quite likely. But it doesn't bolster your case and has absolutely >> > nothing to do with bugzilla shenanagins. >> >> Since when having options is something bad? An http gateway would be a >> great step forward (you could report bugs from any machine in the event >> the one you have to report against cannot even be booted) and the above >> report demonstrates the needing of alternatives to the usual reportbug >> system. > > We should be clear that the referenced bug report proposes being able to > submit *email* to bugs.debian.org via http. As an alternative transport > system it may have advantages for some people in some cirumstances, port > 25 being blocked, for example. Yes, that's one of the limitations of the current system. > So that could be regarded as a good option but it does not involve > anything like web forms, scripts, HTML5 etc. In other words, it would > be business as usual for the 'reportbug system'. Yes, but I take it as a starting point. In the future these new additions could be used to develop an http gateway for reportbug or could also be used as the base to make a complete re-design of the current bug reporting tool... that's what I said. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.10.12.13.43...@gmail.com
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
On Wed 12 Oct 2011 at 10:30:53 +, Camaleón wrote: > On Tue, 11 Oct 2011 19:58:27 +0100, Brian wrote: > > > Quite likely. But it doesn't bolster your case and has absolutely > > nothing to do with bugzilla shenanagins. > > Since when having options is something bad? An http gateway would be a > great step forward (you could report bugs from any machine in the event > the one you have to report against cannot even be booted) and the above > report demonstrates the needing of alternatives to the usual reportbug > system. We should be clear that the referenced bug report proposes being able to submit *email* to bugs.debian.org via http. As an alternative transport system it may have advantages for some people in some cirumstances, port 25 being blocked, for example. So that could be regarded as a good option but it does not involve anything like web forms, scripts, HTML5 etc. In other words, it would be business as usual for the 'reportbug system'. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111012131230.GN23580@desktop
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
On Tue, 11 Oct 2011 16:26:09 -0600, Bob Proulx wrote: > Camaleón wrote: >> Bob Proulx wrote: >> > (shock, surprise) You are saying that filling out a web form in a >> > browser can run processes on the local host machine and send data to >> > the internet? No it can't or it would be a severe security >> > vulnerability. Please list any browser that allows this so that I can >> > file the appropriately severe security bugs against them. >> >> With todays html5 specs out there and a capable browser? I wouldn't put >> my hand on fire for that. And have you recently heard about GNOME and >> javascript capabilities? They allow doing amazing things over a >> browser. > > I admit that I know little yet of HTML5. Although one should never > doubt the power of stupid people in large groups I cannot believe that > HTML5 has been allowed to open such deep security holes in the system. Yes, it can be true to believe but they are here and gnome3 in join with gkt+ 3.2 and javascript is starting to make it firsts steps. You can read more on the usuil IT press/blogs and related developer mailing lists. > My confidence there and believe that it would have been Slashdot'd > widely tells me that it can't yet have happened. Therefore I continue > to believe that it isn't true until proven otherwise. It won't be me who persuades you about that :-) >> Besides, I'm sure you know that flash player plugin can contact you >> webcam and audio devices very easily. > > Is that true on an ARM based platform? Remember that Debian supports a > large number of architectures. AFAIK there is no Adobe Flash available > for ARM based systems. And what has ARM to do with this? Are you running an ARM based machine? Yes? Then good for you :-) But people running flash player on their systems are subject to that type of scannings. > Is that true with Gnash (GNU Flash)? Gnash is the only flash player on > my main desktop (although other machines of mine have the Adobe > proprietary player). (Although I mentioned ARM above my main desktop is > amd64. I didn't want to be misleading here. But I do have ARM based > systems.) Good, but again, are we talking about "you" specifically or we are taking a more wide user case? I am telling you what happens right now with technology that is available in our systems, I can't speak for every concrete desktop there is on the earth as you can understand... > I am not as familiar but I believe even the Adobe Flash player operates > within some containment of access, even if it is self-imposed and > therefore open to attacks and vulnerabilities. If I had my wishes there > would be no Flash based web sites. To be sincere, I don't care about flash player very much, just put it as an example of what can be done with a small plugin and a browser. >> So, if that's something missing in Bugzilla (or another bug tracking >> systems), it should be easily to add although I seriously doubt about >> its usefulness. > > It has a high usefulness, although as a convenience. A BTS bug report > is nothing more than an email message. A user can always follow > instructions instead and create the email message fully manually. Ha! > How often do people actually follow instructions? That is the entire > reason for the bug helpers. Bugzilla (and related web based bug tracking systems) also provides wizards which guide the user to write the report. It's the same as reportbug, you can customize the level of help you want to receive and set that level as the default for the next time. > But I disagree completely here that a web browser filling in a web form > has access to the local system as it is intended to be impossible by > design and security layers to run local programs across the local > filesystem as a web form. Note that Javascript runs inside a security > layer and is restricted from this access. Oh, come on, is not that hard. In the worst scenario, you can tell the user to download a script with instructions to run it and then send the output to a file to be uploaded with the report. That's all. It's possible, easy and convenient for the user that can run the script when he/she wants and attach it to the bug later, when there is Internet connection, for example. >> > I have never ever seen reportbug crash. >> >> You must be then a happy camper and the luckiest person in the hill. > > Are you sure we are talking about 'reportbug'? The last time I run I called "reportbug", not sure if that command will point to something else. Hum... it goes to /usr/bin/reportbug. > It was suggested by another that perhaps you were using 'reportbug-ng' > instead which appears to be a Qt4 GUI based application. I don't thin so, it's plain "reportbug". > Do you have a .reportbugrc file? (I do not.) Yes. > What are the contents? I can't copy the full file because I'm in another computer but it has the usual lines: version, mode expert, ui text, from name, e-mail,smtphost, smtphos
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
On Tue, 11 Oct 2011 19:58:27 +0100, Brian wrote: > On Tue 11 Oct 2011 at 16:37:17 +, Camaleón wrote: > >> And I see there is a bug report for having an http alternative: >> >> support for submitting bug reports via http >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590214 > > A quote from that link (which Stefano Zacchiroli went on to support): > >On Sat, Jul 24, 2010 at 11:50:36PM +0100, Ben Hutchings wrote: >> On Sat, 2010-07-24 at 15:06 -0400, Holger Levsen wrote: >> > So, to summarize: a.) I still think reportbug should be able to >> > submit bugs using port 80 > > Note: you cannot escape using reportbug. I prefer something like bugzilla, yes, but having an http gateway to reportbug is an option I would use more that the application itself, unless it presents the same errors or instabilities. And adding this "addon" to make reportbug allows posting via http or standard protocols will make that possibility even more easy to implement in a future. >> Oh man, that will be great! :-Da > > Quite likely. But it doesn't bolster your case and has absolutely > nothing to do with bugzilla shenanagins. Since when having options is something bad? An http gateway would be a great step forward (you could report bugs from any machine in the event the one you have to report against cannot even be booted) and the above report demonstrates the needing of alternatives to the usual reportbug system. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.10.12.10.30...@gmail.com
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
Camaleón wrote: > Bob Proulx wrote: > > (shock, surprise) You are saying that filling out a web form in a > > browser can run processes on the local host machine and send data to the > > internet? No it can't or it would be a severe security vulnerability. > > Please list any browser that allows this so that I can file the > > appropriately severe security bugs against them. > > With todays html5 specs out there and a capable browser? I wouldn't put > my hand on fire for that. And have you recently heard about GNOME and > javascript capabilities? They allow doing amazing things over a browser. I admit that I know little yet of HTML5. Although one should never doubt the power of stupid people in large groups I cannot believe that HTML5 has been allowed to open such deep security holes in the system. My confidence there and believe that it would have been Slashdot'd widely tells me that it can't yet have happened. Therefore I continue to believe that it isn't true until proven otherwise. > Besides, I'm sure you know that flash player plugin can contact you > webcam and audio devices very easily. Is that true on an ARM based platform? Remember that Debian supports a large number of architectures. AFAIK there is no Adobe Flash available for ARM based systems. Is that true with Gnash (GNU Flash)? Gnash is the only flash player on my main desktop (although other machines of mine have the Adobe proprietary player). (Although I mentioned ARM above my main desktop is amd64. I didn't want to be misleading here. But I do have ARM based systems.) I am not as familiar but I believe even the Adobe Flash player operates within some containment of access, even if it is self-imposed and therefore open to attacks and vulnerabilities. If I had my wishes there would be no Flash based web sites. > But there is no bug nor security flaws here, because the user agrees > in being scanned ;-) On that point I agree. When the user-admin installs something they implicitly agree to it. > So, if that's something missing in Bugzilla (or another bug tracking > systems), it should be easily to add although I seriously doubt about its > usefulness. It has a high usefulness, although as a convenience. A BTS bug report is nothing more than an email message. A user can always follow instructions instead and create the email message fully manually. Ha! How often do people actually follow instructions? That is the entire reason for the bug helpers. But I disagree completely here that a web browser filling in a web form has access to the local system as it is intended to be impossible by design and security layers to run local programs across the local filesystem as a web form. Note that Javascript runs inside a security layer and is restricted from this access. > But no, I was not referring to that specific ability of reportbug (which > I still find a bit intrusive) but the option for looking into another > bugs already opened for the same issue. I always search the BTS myself first to look for problems before reporting them. Then when I do invoke reportbug I invoke it with the --no-query-bts option to avoid that interaction. $ reportbug -b somepackage Looking now I see that it is possible to put this into the $HOME/.reportbugrc file and make it the default. I have now done so as a convenience. > >> And bugzilla does not tend to crash when writing bug reports >:-) > >> > >> In fact, I usually avoid using "reportbug" because of its high > >> instability (it's annoying having to re-do a full report several > >> times...) and finally send the report "manually" -by e-mail- which is > >> not a task for newcomers neither encourages people to write bug reports > >> ;-( > > > > I have never ever seen reportbug crash. > > You must be then a happy camper and the luckiest person in the hill. Are you sure we are talking about 'reportbug'? It was suggested by another that perhaps you were using 'reportbug-ng' instead which appears to be a Qt4 GUI based application. Do you have a .reportbugrc file? (I do not.) What are the contents? Try moving it out of the way and running without local customization. $ mv ~/.reportbugrc reportbugrc.suspect $ reportbug -b somepackage Since reportbug simply guides the user through sending an email the design of it is very simple. Ask a couple of questions. Build an email template. Start an editor for the user to finish filling out the email. Send the email. Although bugs exist in almost every program that seems too simple to crash. Launching the editor seems to me like the most risky part since people can choose anything and some of the choices could be quite problematic. > > Since it is just a python script I would think that an actual crash > > would be quite difficult. > > Err... that must be because you have never seen it explode in front of > your face :-) Correct. > > I am hoping you filed a bug report on reportbug crashing! :-) > > I think no more.
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
On Tue 11 Oct 2011 at 16:37:17 +, Camaleón wrote: > And I see there is a bug report for having an http alternative: > > support for submitting bug reports via http > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590214 A quote from that link (which Stefano Zacchiroli went on to support): On Sat, Jul 24, 2010 at 11:50:36PM +0100, Ben Hutchings wrote: > On Sat, 2010-07-24 at 15:06 -0400, Holger Levsen wrote: > > So, to summarize: a.) I still think reportbug should be able to submit bugs > > using port 80 Note: you cannot escape using reportbug. > Oh man, that will be great! :-Da Quite likely. But it doesn't bolster your case and has absolutely nothing to do with bugzilla shenanagins. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111011185827.GJ23580@desktop
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
On Mon 10 Oct 2011 at 17:50:10 -0600, Bob Proulx wrote: > Camaleón wrote: > > > And bugzilla does not tend to crash when writing bug reports >:-) > > > > In fact, I usually avoid using "reportbug" because of its high > > instability (it's annoying having to re-do a full report several > > times...) and finally send the report "manually" -by e-mail- which is not > > a task for newcomers neither encourages people to write bug reports ;-( > > I have never ever seen reportbug crash. Since it is just a python > script I would think that an actual crash would be quite difficult. Whether reportbug works flawlessly or not for everyone is immaterial to any argument expressing a desire for a web based interface to the BTS. The BTS accepts email submissions only and even if reportbug worked for nobody the BTS will still accept bug reports. So I, for one, remain unclear as to why a web form is desirable for the submission of a bug report. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111011184244.GI23580@desktop
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
On Tue, 11 Oct 2011 10:57:50 -0400, Celejar wrote: > On Tue, 11 Oct 2011 12:15:46 + (UTC) Camaleón > wrote: > >> On Mon, 10 Oct 2011 17:50:10 -0600, Bob Proulx wrote: >> >> > Camaleón wrote: >> >> Darac Marjal wrote: > > ... > >> >> And bugzilla does not tend to crash when writing bug reports >:-) >> >> >> >> In fact, I usually avoid using "reportbug" because of its high >> >> instability (it's annoying having to re-do a full report several >> >> times...) and finally send the report "manually" -by e-mail- which >> >> is not a task for newcomers neither encourages people to write bug >> >> reports ;-( >> > >> > I have never ever seen reportbug crash. >> >> You must be then a happy camper and the luckiest person in the hill. > > I can't recall the last time (if ever) that I had a reportbug crash > (usually running uptodate Sid). It's okay that you have not experienced any error when running sid's reportbug, but let people who indeed do have had express their frustation :-) I can assure you the last thing I like is criticizing a program but when something crashes many times in front of your face and you have been recollecting detailed information to write a good bug report... well, is not a very nice experience. And I see there is a bug report for having an http alternative: support for submitting bug reports via http http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590214 Oh man, that will be great! :-D Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.10.11.16.37...@gmail.com
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
On Tue, 11 Oct 2011 12:15:46 + (UTC) Camaleón wrote: > On Mon, 10 Oct 2011 17:50:10 -0600, Bob Proulx wrote: > > > Camaleón wrote: > >> Darac Marjal wrote: ... > >> And bugzilla does not tend to crash when writing bug reports >:-) > >> > >> In fact, I usually avoid using "reportbug" because of its high > >> instability (it's annoying having to re-do a full report several > >> times...) and finally send the report "manually" -by e-mail- which is > >> not a task for newcomers neither encourages people to write bug reports > >> ;-( > > > > I have never ever seen reportbug crash. > > You must be then a happy camper and the luckiest person in the hill. I can't recall the last time (if ever) that I had a reportbug crash (usually running uptodate Sid). Celejar -- foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111011105750.0dde7d9cf445254e41ba6...@gmail.com
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
On Mon, Oct 10, 2011 at 8:38 PM, Bob Proulx wrote: > > 3. Reportbug sends the bug report bug using /usr/sbin/sendmail as the > MTA. If that doesn't work then reportbug (and other commands too) > will have problems. I have no workaround to /usr/sbin/sendmail not > working. That simply must work for a healthy system. If that is > the problem then solve that problem first. You can use gmail (or another "external" smtp server) to send a report. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=SyAtgHo7mE=V5Xh2Òz98vfcoog1tri_nrrmgjca-...@mail.gmail.com
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
On Mon, 10 Oct 2011 17:50:10 -0600, Bob Proulx wrote: > Camaleón wrote: >> Darac Marjal wrote: >> > While a web-based interface may be nice, I think that where debian's >> > bug reporting excels is in the 'reportbug' program. It's not just a >> > program that sends emails to a single address, but it provides a good >> > guide through the bug-reporting process, namely encouraging you to >> > check that the bug is not already raised, checking that the version >> > of the package you're reporting against isn't out of date and also >> > collecting useful information for the developers (changed >> > configuration, usually). >> >> Did you recently fill a bug on a bugzilla-alike bug tracking system? >> >> It does not only allows what you mention but it enhances the reporter >> experience by allowing a higher level of configuration and >> customization on almost any aspect, not only for the UI (bugs alerts >> are just great). >> >> > Some of that, a web based solution just can't do (as easily). >> >> Ha! Of course it can. > > (shock, surprise) You are saying that filling out a web form in a > browser can run processes on the local host machine and send data to the > internet? No it can't or it would be a severe security vulnerability. > Please list any browser that allows this so that I can file the > appropriately severe security bugs against them. With todays html5 specs out there and a capable browser? I wouldn't put my hand on fire for that. And have you recently heard about GNOME and javascript capabilities? They allow doing amazing things over a browser. Besides, I'm sure you know that flash player plugin can contact you webcam and audio devices very easily. But there is no bug nor security flaws here, because the user agrees in being scanned ;-) So, if that's something missing in Bugzilla (or another bug tracking systems), it should be easily to add although I seriously doubt about its usefulness. But no, I was not referring to that specific ability of reportbug (which I still find a bit intrusive) but the option for looking into another bugs already opened for the same issue. >> And bugzilla does not tend to crash when writing bug reports >:-) >> >> In fact, I usually avoid using "reportbug" because of its high >> instability (it's annoying having to re-do a full report several >> times...) and finally send the report "manually" -by e-mail- which is >> not a task for newcomers neither encourages people to write bug reports >> ;-( > > I have never ever seen reportbug crash. You must be then a happy camper and the luckiest person in the hill. > Since it is just a python script I would think that an actual crash > would be quite difficult. Err... that must be because you have never seen it explode in front of your face :-) > I am hoping you filed a bug report on reportbug crashing! :-) I think no more. I'm tired. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.10.11.12.15...@gmail.com
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
Disc Magnet wrote: > It usually hangs whenever I launch reportbug and click on some other > window (thus report bug becoming the inactive window). When I click on > reportbug again, it is found to be in hung state. It doesn't respond > at all. I think you are using reportbug-ng, not reportbug. I can't reproduce your problem (fvwm, Sid on AMD64). -- John Hasler -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87d3e4fhlj@thumper.dhh.gt.org
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
Disc Magnet wrote: > Bob Proulx wrote: > > I have never ever seen reportbug crash. Since it is just a python > > script I would think that an actual crash would be quite difficult. > > > > I am hoping you filed a bug report on reportbug crashing! :-) > > reportbug hangs at the drop of a hat on my system. and then I have to > figure how to file a bug about reportbug. It usually hangs whenever I > launch reportbug and click on some other window (thus report bug > becoming the inactive window). When I click on reportbug again, it is > found to be in hung state. It doesn't respond at all. That is really odd. I believe you. But how would there be any interaction with the state of window focus or have any interaction with the mouse at all? That sounds like a window manager bug. What terminal program are you using? gnome-terminal? konsole? I am using xterm and I have never seen xterm hang in this situation. You may have hit a terminal bug of some sort. Try launching it from an xterm and seeing if the problem can be recreated there. If not then that would point to the other terminal program. Some thoughts come to mind. 1. Reportbug spawns $EDITOR / $VISUAL to enter data. If your $EDITOR hangs then of course reportbug is blocked behind it. Looking at the process parent-child hierarchy should reveal this problem. ps -efH | less +/reportbug From that it should be possible to know if reportbug has spawned a sub-process or not. Try a simpler editor. I am using emacs proving that complex editors work fine. But if you are using some graphical editor then I could see a bug there appearing as a reportbug hang but really being an editor problem. reportbug --editor=nano 2. Reportbug talks to the bugs.debian.org and to packages.debian.org over the network. If those queries delay then this may appear as a hang. If an http proxy has been set then problems with the proxy could appear through reportbug. Try running reportbug with --offline. That will prevent querying the bts for other bug report and will prevent looking to see if there is a newer version of the package available. reportbug --offline PACKAGENAME 3. Reportbug sends the bug report bug using /usr/sbin/sendmail as the MTA. If that doesn't work then reportbug (and other commands too) will have problems. I have no workaround to /usr/sbin/sendmail not working. That simply must work for a healthy system. If that is the problem then solve that problem first. 4. You are not using the --ui=gtk2 option are you? Launched like this? reportbug --ui=gtk2 If so try it without specifying that option. Bob signature.asc Description: Digital signature
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
On Tue, Oct 11, 2011 at 5:20 AM, Bob Proulx wrote: > Camaleón wrote: >> Darac Marjal wrote: >> > While a web-based interface may be nice, I think that where debian's bug >> > reporting excels is in the 'reportbug' program. It's not just a program >> > that sends emails to a single address, but it provides a good guide >> > through the bug-reporting process, namely encouraging you to check that >> > the bug is not already raised, checking that the version of the package >> > you're reporting against isn't out of date and also collecting useful >> > information for the developers (changed configuration, usually). >> >> Did you recently fill a bug on a bugzilla-alike bug tracking system? >> >> It does not only allows what you mention but it enhances the reporter >> experience by allowing a higher level of configuration and customization >> on almost any aspect, not only for the UI (bugs alerts are just great). >> >> > Some of that, a web based solution just can't do (as easily). >> >> Ha! Of course it can. > > (shock, surprise) You are saying that filling out a web form in a > browser can run processes on the local host machine and send data to > the internet? No it can't or it would be a severe security > vulnerability. Please list any browser that allows this so that I can > file the appropriately severe security bugs against them. > >> And bugzilla does not tend to crash when writing bug reports >:-) >> >> In fact, I usually avoid using "reportbug" because of its high >> instability (it's annoying having to re-do a full report several >> times...) and finally send the report "manually" -by e-mail- which is not >> a task for newcomers neither encourages people to write bug reports ;-( > > I have never ever seen reportbug crash. Since it is just a python > script I would think that an actual crash would be quite difficult. > > I am hoping you filed a bug report on reportbug crashing! :-) > > Bob > reportbug hangs at the drop of a hat on my system. and then I have to figure how to file a bug about reportbug. It usually hangs whenever I launch reportbug and click on some other window (thus report bug becoming the inactive window). When I click on reportbug again, it is found to be in hung state. It doesn't respond at all. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cala9zswx68jcoqzovemu4_qnf3xpjzbminzy4ydxb7yck_x...@mail.gmail.com
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
Camaleón wrote: > Darac Marjal wrote: > > While a web-based interface may be nice, I think that where debian's bug > > reporting excels is in the 'reportbug' program. It's not just a program > > that sends emails to a single address, but it provides a good guide > > through the bug-reporting process, namely encouraging you to check that > > the bug is not already raised, checking that the version of the package > > you're reporting against isn't out of date and also collecting useful > > information for the developers (changed configuration, usually). > > Did you recently fill a bug on a bugzilla-alike bug tracking system? > > It does not only allows what you mention but it enhances the reporter > experience by allowing a higher level of configuration and customization > on almost any aspect, not only for the UI (bugs alerts are just great). > > > Some of that, a web based solution just can't do (as easily). > > Ha! Of course it can. (shock, surprise) You are saying that filling out a web form in a browser can run processes on the local host machine and send data to the internet? No it can't or it would be a severe security vulnerability. Please list any browser that allows this so that I can file the appropriately severe security bugs against them. > And bugzilla does not tend to crash when writing bug reports >:-) > > In fact, I usually avoid using "reportbug" because of its high > instability (it's annoying having to re-do a full report several > times...) and finally send the report "manually" -by e-mail- which is not > a task for newcomers neither encourages people to write bug reports ;-( I have never ever seen reportbug crash. Since it is just a python script I would think that an actual crash would be quite difficult. I am hoping you filed a bug report on reportbug crashing! :-) Bob signature.asc Description: Digital signature
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
On Mon 10 Oct 2011 at 11:42:50 +0100, Darac Marjal wrote: > On Sat, Oct 08, 2011 at 11:04:07AM +, Camaleón wrote: > > > > I'd like to see a web based interface for reporting bugs in Debian, while > > I find reporting by e-mail a very nice (must have) option, bugzilla-alike > > based interfaces are also very easy to deal with (for the reporter) and > > plenty of nice features. > > While a web-based interface may be nice, I think that where debian's bug > reporting excels is in the 'reportbug' program. It's not just a program > that sends emails to a single address, but it provides a good guide > through the bug-reporting process, namely encouraging you to check that > the bug is not already raised, checking that the version of the package > you're reporting against isn't out of date and also collecting useful > information for the developers (changed configuration, usually). You have expressed this well and highlighted how reportbug fits the design, function and philosophy of the BTS. A nice, easy to use or user-friendly interface is not part of the picture. It happens that a combination of reportbug+vim+mutt does display all these three aspects but . . . . :) > Some of that, a web based solution just can't do (as easily). Probably not at all easily. Maybe impossible. But I'm not an expert. In the event it is not going to happen as it would meet with fierce resistance. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111010183222.GH23580@desktop
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
On Mon, 10 Oct 2011 11:42:50 +0100, Darac Marjal wrote: > On Sat, Oct 08, 2011 at 11:04:07AM +, Camaleón wrote: (...) >> I'd like to see a web based interface for reporting bugs in Debian, >> while I find reporting by e-mail a very nice (must have) option, >> bugzilla-alike based interfaces are also very easy to deal with (for >> the reporter) and plenty of nice features. > > While a web-based interface may be nice, I think that where debian's bug > reporting excels is in the 'reportbug' program. It's not just a program > that sends emails to a single address, but it provides a good guide > through the bug-reporting process, namely encouraging you to check that > the bug is not already raised, checking that the version of the package > you're reporting against isn't out of date and also collecting useful > information for the developers (changed configuration, usually). Did you recently fill a bug on a bugzilla-alike bug tracking system? It does not only allows what you mention but it enhances the reporter experience by allowing a higher level of configuration and customization on almost any aspect, not only for the UI (bugs alerts are just great). > Some of that, a web based solution just can't do (as easily). Ha! Of course it can. And bugzilla does not tend to crash when writing bug reports >:-) In fact, I usually avoid using "reportbug" because of its high instability (it's annoying having to re-do a full report several times...) and finally send the report "manually" -by e-mail- which is not a task for newcomers neither encourages people to write bug reports ;-( Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.10.10.12.02...@gmail.com
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
On Sat, Oct 08, 2011 at 11:04:07AM +, Camaleón wrote: > On Fri, 07 Oct 2011 22:01:11 +0200, Frank Lanitz wrote: > > > Is there any issue known with reportbug in unstable/bugs.debian.org? > > Somehow I don't receive an response with a bug number when submitting a > > bugreport > > If you receive no bug number it could be because the report was not > properly sent. Did you get any error at any stage of the process? Did you > confirm the existance of the report by manually browsing BTS? > > I'd like to see a web based interface for reporting bugs in Debian, while > I find reporting by e-mail a very nice (must have) option, bugzilla-alike > based interfaces are also very easy to deal with (for the reporter) and > plenty of nice features. While a web-based interface may be nice, I think that where debian's bug reporting excels is in the 'reportbug' program. It's not just a program that sends emails to a single address, but it provides a good guide through the bug-reporting process, namely encouraging you to check that the bug is not already raised, checking that the version of the package you're reporting against isn't out of date and also collecting useful information for the developers (changed configuration, usually). Some of that, a web based solution just can't do (as easily). -- Darac Marjal signature.asc Description: Digital signature
Re: Is there any issue with reportbug in unstabl or bugs.debian.org?
On Fri, 07 Oct 2011 22:01:11 +0200, Frank Lanitz wrote: > Is there any issue known with reportbug in unstable/bugs.debian.org? > Somehow I don't receive an response with a bug number when submitting a > bugreport If you receive no bug number it could be because the report was not properly sent. Did you get any error at any stage of the process? Did you confirm the existance of the report by manually browsing BTS? I'd like to see a web based interface for reporting bugs in Debian, while I find reporting by e-mail a very nice (must have) option, bugzilla-alike based interfaces are also very easy to deal with (for the reporter) and plenty of nice features. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.10.08.11.04...@gmail.com
