Re: [DNG] reportbug default bts

dear Nate, On Sat, 10 Jun 2017, Nate Bargmann wrote: > I emailed a followup to 6...@bugs.devuan.org and received an > acknowledgment from the BTS but the message has not appeared on the > bug's Web page. I have the same problem and this and other issues were addressed in our last developer

Re: [DNG] reportbug default bts

I emailed a followup to 6...@bugs.devuan.org and received an acknowledgment from the BTS but the message has not appeared on the bug's Web page. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Ham radio, Linux, bikes, and

Re: [DNG] reportbug default bts

* On 2017 05 Jun 02:07 -0500, KatolaZ wrote: > Hi Nate, > > thanks for your email. The issue is known. That string is saying you > that reportbug was unable to fetch existing relevant bugs from > bugs.devuan.org. The reason is that reportbug expects to find a SOAP > service running on

Re: [DNG] reportbug default bts

On Mon, Jun 05, 2017 at 08:06:44AM +0100, KatolaZ wrote: [cut] > > We must retain the useful functionalities, avoiding to get absolutely > everything on board, since there is also a kitchen sink, a washing > machine, an maybe a crocodile or two in there...:) > > In the same spirit, I am also

Re: [DNG] reportbug default bts

On Sun, Jun 04, 2017 at 10:00:03PM -0500, Nate Bargmann wrote: [cut] > > > Nevermind that my email address is incorrect as I had not yet created a > $HOME/.reportbugrc on that computer. > > I did create $HOME/.reportbugrc and uncommented the line of "bts > devuan", set my email, realname, and

Re: [DNG] reportbug default bts

I just ran into a similar issue trying to use reportbug on a computer I installed Devuan 1.0 Stable a week ago today using the Netinstall ISO. Here is what happened when running reportbug for the first time: $ reportbug flashplugin-nonfree Warning: no reportbug configuration found. Proceeding

Re: [DNG] reportbug default bts

Am 2017-05-15 06:36, schrieb Steve Litt: Perhaps not in De**an, but in other distros, I've seen things go to hell in a handbasket when trying to upgrade to the next major version. I think here is a little bit confusion about what a "dist-upgrade" is and does. It *can* be used for upgrade to a

Re: [DNG] reportbug default bts

On Sun, 14 May 2017 20:39:25 +0100 KatolaZ wrote: > On Sun, May 14, 2017 at 11:49:14AM -0400, Steve Litt wrote: > > [cut] > > > > > No it doesn't. apt get dist-upgrade must pay attention to your > > current config files, some of which might have been constructed > > four

Re: [DNG] reportbug default bts

On Sun, May 14, 2017 at 11:49:14AM -0400, Steve Litt wrote: [cut] > > No it doesn't. apt get dist-upgrade must pay attention to your current > config files, some of which might have been constructed four major > versions ago and have little current relevance. After dist-upgrade, > you're very

Re: [DNG] reportbug default bts

> > > -- > > Message: 6 > Date: Sun, 14 May 2017 10:10:19 -0400 > From: fsmithred <fsmith...@gmail.com> > To: dng@lists.dyne.org > Subject: Re: [DNG] reportbug default bts > Message-ID: <ea48b39e-7a32-e773-dad3-3a05090bc...@gmail.c

Re: [DNG] reportbug default bts

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, 14 May 2017 11:49:14 -0400 Steve Litt wrote: > This concern that you characterize as a "myth" is something I read in > various apt package distro mailing lists on a somewhat regular basis. > I also have one

Re: [DNG] reportbug default bts

On Sun, 14 May 2017 12:26:51 +0200 Joachim Fahrner wrote: > Am 2017-05-14 08:23, schrieb KatolaZ: > > > > again, there is nothing to fear in dist-upgrade... > > That's right. I'm using Debian/Devuan since many years and never had > a problem with dist-upgrade. I'm

Re: [DNG] reportbug default bts

Le 14/05/2017 à 16:10, fsmithred a écrit : On 05/13/2017 11:03 AM, Steve Litt wrote: On Sat, 13 May 2017 01:06:38 -1000 Joel Roth wrote: Long before three weeks ago. I don't usually upgrade or dist-upgrade unless there is some particular need. Probably I'm not alone, even if

Re: [DNG] reportbug default bts

On 05/13/2017 11:03 AM, Steve Litt wrote: > On Sat, 13 May 2017 01:06:38 -1000 > Joel Roth wrote: > >> Long before three weeks ago. I don't usually upgrade or >> dist-upgrade unless there is some particular need. >> Probably I'm not alone, even if that is not considered >> best

Re: [DNG] reportbug default bts

On Sun, May 14, 2017 at 02:23:50PM +0200, Didier Kryn wrote: > >On Sun, May 14, 2017 at 08:08:51AM +0200, Didier Kryn wrote: > > > >[cut] > > > >> apt-get dist-upgrade is what's necessary to change release - as the > >> name > >>means -, eg Wheezy to Jessie or Jessie to Ascii. > >or if

Re: [DNG] reportbug default bts

Am 2017-05-14 08:23, schrieb KatolaZ: again, there is nothing to fear in dist-upgrade... That's right. I'm using Debian/Devuan since many years and never had a problem with dist-upgrade. I'm wondering about this myth that dist-upgrade could break something. dist-upgrade has the same effect

Re: [DNG] reportbug default bts

On Sun, May 14, 2017 at 08:08:51AM +0200, Didier Kryn wrote: [cut] > > apt-get dist-upgrade is what's necessary to change release - as the name > means -, eg Wheezy to Jessie or Jessie to Ascii. or if you are permanently on testing, since it is not uncommon there for some upgrades to

Re: [DNG] reportbug default bts

Le 13/05/2017 à 17:03, Steve Litt a écrit : On Sat, 13 May 2017 01:06:38 -1000 Joel Roth wrote: Long before three weeks ago. I don't usually upgrade or dist-upgrade unless there is some particular need. Probably I'm not alone, even if that is not considered best practice. I

Re: [DNG] reportbug default bts

Steve Litt [2017-05-13 17:03]: > I never dist-upgrade. From what I hear, it breaks things. If I feel the > need to dist-upgrade, it's probably time to back up, reformat the > disks, and clean-install a later version. If you can't dist-upgrade, it's probably time to find another distribution. --

Re: [DNG] reportbug default bts

On Sat, May 13, 2017 at 07:36:32PM +0200, Arnt Karlsen wrote: > > ..I came in woody time from the cold dropped Red Hat 7.3, I've > dist-upgraded from woody and sarge to sid/wheezy, and from lenny > to sid/Jessie. Only reason I left SuSE-5.2 (It rocked!), was > I didn't know how to do "insmod

Re: [DNG] reportbug default bts

On Sat, 13 May 2017 16:16:48 +0100, KatolaZ wrote in message <20170513151648.gf14...@katolaz.homeunix.net>: > On Sat, May 13, 2017 at 11:03:18AM -0400, Steve Litt wrote: > > On Sat, 13 May 2017 01:06:38 -1000 > > Joel Roth wrote: > > > > > Long before three weeks ago. I don't

Re: [DNG] reportbug default bts

On Sat, May 13, 2017 at 11:03:18AM -0400, Steve Litt wrote: > On Sat, 13 May 2017 01:06:38 -1000 > Joel Roth wrote: > > > Long before three weeks ago. I don't usually upgrade or > > dist-upgrade unless there is some particular need. > > Probably I'm not alone, even if that is

Re: [DNG] reportbug default bts

On Sat, 13 May 2017 01:06:38 -1000 Joel Roth wrote: > Long before three weeks ago. I don't usually upgrade or > dist-upgrade unless there is some particular need. > Probably I'm not alone, even if that is not considered > best practice. I never dist-upgrade. From what I hear,

Re: [DNG] reportbug default bts

On Sat, May 13, 2017 at 01:06:38AM -1000, Joel Roth wrote: [cut] > > Hi Joel, > > > > that's strange again. Do you remember when you dist-upgraded? > > reportbug-6.6.3+devuan1.3 has been in the repos since about three > > weeks ago... > > Long before three weeks ago. I don't usually upgrade or

Re: [DNG] reportbug default bts

KatolaZ wrote: > On Fri, May 12, 2017 at 11:11:06PM -1000, Joel Roth wrote: [cut] > > Somehow my upgrade to Devuan somehow missed getting reportbug. > > > > $ dpkg -l reportbug > > > > Desired=Unknown/Install/Remove/Purge/Hold > > | > >

Re: [DNG] reportbug default bts

On Fri, May 12, 2017 at 11:11:06PM -1000, Joel Roth wrote: [cut] > > Hi KatolaZ, > > Somehow my upgrade to Devuan somehow missed getting reportbug. > > $ dpkg -l reportbug > > Desired=Unknown/Install/Remove/Purge/Hold > |

Re: [DNG] reportbug default bts

On Sat, May 13, 2017 at 05:54:13AM +0100, KatolaZ wrote: > On Fri, May 12, 2017 at 03:41:23PM -1000, Joel Roth wrote: > > [cut] > > > > > When I ran reportbug and filed a bug, I was surprised to > > see the report went to Debian. > > > > /etc/reportbug.conf (which I've never edited) > > has

Re: [DNG] reportbug default bts

On Fri, May 12, 2017 at 03:41:23PM -1000, Joel Roth wrote: [cut] > > When I ran reportbug and filed a bug, I was surprised to > see the report went to Debian. > > /etc/reportbug.conf (which I've never edited) > has no bts setting. > > $ reportbug --bts help > > Valid bug tracking systems:

[DNG] reportbug default bts

Hi, I'm running Devuan/Jessie, having migrated from Debian/Jessie. Being advised to file bugs at bugs.devuan.org, I viewed the site, which recommends using reportbug as the preferred way to report bugs. When I ran reportbug and filed a bug, I was surprised to see the report went to Debian.