On Tue, May 01, 2018 at 02:45:00PM +0200, Arnt Karlsen wrote: [cut]
> > > Is this the normal way you interact with an open-source community, or > > are you making some special effort to look mean just for Devuan? :\ > > ..this in how I repond to people who whine. Also in courts. > wow. Except you are the only one whining here :) > ..regardless of whether or not I am right or wrong about things being > broken, I report on things I suspect may be broken, because they appear > broken to me, and because I belive broken stuff in Devuan needs to be > fixed, regardless of whether I can do it myself, or of my need for > funds to hire a lawyer to do my post-Groklaw litigation, or whatever. > double-wow. I am seriously impressed :) > ..human error is part of the deal, deal with it. > good advice for anybody, indeed. > > > ~$ reportbug edb > > > *** Welcome to reportbug. Use ? for help at prompts. *** > > > Note: bug reports are publicly archived (including the email > > > address of the submitter). Detected character set: UTF-8 > > > Please change your locale if this is incorrect. > > > > > > Using 'arnt <a...@iaksess.no>' as your from address. > > > Getting status for edb... > > > A package named "edb" does not appear to be installed; do you want > > > to search for a similar-looking filename in an installed package > > > [Y|n|q|?]? n Getting available info for edb... Please enter the > > > version of the package this report applies to (blank OK) > > > > 1.13-3 > > > Will send report to Devuan (per lsb_release). > > > Querying Devuan BTS for reports on edb (source)... > > > Unable to connect to Devuan BTS (error: "NoNetwork()"); continue > > > [y|N|?]? > > > > > > > Now the BTS is broken...except it ain't broken (and the fact that many > > users have been able to use it should be a hint). It's just telling > > you that it can't retrieve the list of bugs related to that > > package. That's because the "feature" is currently disabled. > > ..why??? This edb bug is > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840748 and is not yet > solved in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871041 ... > > ...and we shouldn't have to waste effort on needlessly creating > duplicate bug reports, if we can drop them right home (upstream > in this case) where they belong. > The reason is simple: the BTS (debbugs) has been developed by Debian for Debian. It is a quite hairy ball of spaghetti stuff, written in four different languages by dozens of people over about 25 years, and, believe it or not, it is *quite difficult* to customise. If you have a solution for that, any help will be more than welcome. I haven't been able to find a way to do that which does not require binning debbugs and using something else. Maybe it's the sane thing to do. But "using something else" requires time in testing, porting, deploying, and maintaining. And we simple haven't had the required energy to do that. You know, we are trying to push ascii out in the meanwhile... > > ..any amprolla style work on separately fetching bugs in progress? > That's not at all related to amprolla, but you are welcome to work on that nevertheless. And to submit code. > ..one way could be use a "Fetch bug reports now?" menu option, and > then add a "Fetch Debian Upstream bug reports now?" menu option, > and then a "Fetch Further Upstream bug reports now?" menu option, > rather than try do it all automatically like Debian's reportbug, > "dumping them all in one big messy bug soup bowl." > Great. The reporository for reportbug (which is a package that has been forked byu Devuan) is available at: https://git.devuan.org/devuan-packages/reportbug Patches are welcome. You'll probably find out by yourself how easy is to delve into reportbug, and how easy it is to change it. > > > Just hit "y" and continue with your bug report. > > ..willco. > > > The list of bugs > > related to a package can be retrieved from bugs.devuan.org > > ..https://bugs.devuan.org//cgi/pkgreport.cgi?which=pkg&data=edb > now reports: " Devuan bug report logs: package edb > There is no record of the edb package, and no bugs have been > filed against it.", possibly because bugs.devuan.org _doesn't_ > check packages that we fetch from Debian, with bugs.debian.org. > > ..if it did, it would mention Debian's #840748 and #871041, > _now_ on Tue, 1 May 2018 11:34:58 UTC, _before_ my report. > I should have said: the list of bugs related to a package forked by Devuan can be retrieved from bugs.devuan.org. We haven't forked edb, and I think we don't have any reason to do that, so you should report the bug upstream (i.e., to Debian) or up-upstream (i.e., to GNU Emacs). HND KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ]
signature.asc
Description: Digital signature
_______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
