Anno domini 2019 Mon, 30 Dec 15:20:50 +
Nicola Orrù via Dng scripsit:
> Hello,
>
> I have reported a few bugs via Reportbug in the last few days. The
> system would usually respond with an automated mail, but I haven't
> received anything.
>
> Also, there is no trace of my bug reports at htt
Hello,
I have reported a few bugs via Reportbug in the last few days. The
system would usually respond with an automated mail, but I haven't
received anything.
Also, there is no trace of my bug reports at https://bugs.devuan.org/
Anyone else experiencing these problems?
--
Cheers,
Nico
___
On Tue, 1 May 2018 14:15:47 +0100, KatolaZ wrote in message
<20180501131547.gl26...@katolaz.homeunix.net>:
> On Tue, May 01, 2018 at 03:11:21PM +0200, Arnt Karlsen wrote:
>
> [cut]
>
> > ...
> >
> > > > Just hit "y" and continue with your bug report.
> > >
> > > ..willco.
> >
> > ..
On Tue, May 01, 2018 at 03:11:21PM +0200, Arnt Karlsen wrote:
[cut]
> ...
>
> > > Just hit "y" and continue with your bug report.
> >
> > ..willco.
>
> ..done, no reponse yet on email nor on:
> https://bugs.devuan.org//cgi/pkgreport.cgi?which=pkg&data=edb
> my bug report is awaiting moderat
On Tue, 1 May 2018 14:45:00 +0200, Arnt wrote in message
<20180501144500.2c5f46f0@d44>:
> On Tue, 1 May 2018 10:02:34 +0100, KatolaZ wrote in message
> <20180501090234.gi26...@katolaz.homeunix.net>:
...
> > Now the BTS is broken...except it ain't broken (and the fact that
> > many users have b
On Sun, Jul 23, 2017 at 05:44:14PM -0400, Boruch Baum wrote:
>
> Funny, Why is it that I only get that kind of response from people who
> only make useless unconstructive and unhelpful comments? It doesn't
> sound that you have been following this thread too closely. The source
> of the problem w
On 2017-07-21 19:06, KatolaZ wrote:
> On Fri, Jul 21, 2017 at 11:45:23AM -0400, Boruch Baum wrote:
> > On 2017-07-22 00:23, Ralph Ronnquist wrote:
> > > Boruch Baum wrote on 21/07/17 23:50:
> > > > Where else should I be looking?
> > >
> > > Perhaps you've set "APT::Default-Release "jessie";" ?
> >
On Fri, 21 Jul 2017 22:21:53 -0400, Hendrik wrote in message
<20170722022153.gb8...@topoi.pooq.com>:
> On Fri, Jul 21, 2017 at 11:45:23AM -0400, Boruch Baum wrote:
>
> > The bad news is that if this is the only step I take, "apt-get" will
> > want to upgrade 1248 packages (it looks more impressi
On Fri, Jul 21, 2017 at 11:45:23AM -0400, Boruch Baum wrote:
> The bad news is that if this is the only step I take, "apt-get" will
> want to upgrade 1248 packages (it looks more impressive when I write it
> out . . One Thousand, Two Hundred and Forty Eight packages) with a
> download size of 608
I wrote:
> All the time, a lot of people we stood on the sidelines willing them to fail.
Oops, s/we/were/
Personally I was watching and thinking "that's one hell of a task, I'm a bit
sceptical* but I sure as heck hope they manage it".
* Not knowing who these veterans were, and their level of sk
Boruch Baum wrote:
> The bad news is that if this is the only step I take, "apt-get" will
> want to upgrade 1248 packages (it looks more impressive when I write it
> out . . One Thousand, Two Hundred and Forty Eight packages) with a
> download size of 608 Mb.
What if, instead of doing "apt-get
On Fri, Jul 21, 2017 at 11:45:23AM -0400, Boruch Baum wrote:
> On 2017-07-22 00:23, Ralph Ronnquist wrote:
> > Boruch Baum wrote on 21/07/17 23:50:
> > > Where else should I be looking?
> >
> > Perhaps you've set "APT::Default-Release "jessie";" ?
> >
> > Without that, you'll get the more balanced
On 2017-07-22 00:23, Ralph Ronnquist wrote:
> Boruch Baum wrote on 21/07/17 23:50:
> > Where else should I be looking?
>
> Perhaps you've set "APT::Default-Release "jessie";" ?
>
> Without that, you'll get the more balanced pinning of 500 and 100.
> I think I saw some Debian bug report (on apt?) fo
Boruch Baum wrote on 21/07/17 23:50:
On 2017-07-21 14:14, KatolaZ wrote:
On Fri, Jul 21, 2017 at 08:39:50AM -0400, Boruch Baum wrote:
Just to clarify, and since you are talking about "default" pin levels:
the default pin level of standard Devuan repositories is 500. The
default for backports
On Fri, Jul 21, 2017 at 09:40:27AM -0400, Boruch Baum wrote:
[cut]
>
> 2] Isn't it a legitimate devuan package from a legitimate currently
>supported devuan repository?
if you are not using the 6.6.3+devuan1.3 version, then it's not a
package in a legitimate currently supported devuna reposi
On 2017-07-21 14:14, KatolaZ wrote:
> On Fri, Jul 21, 2017 at 08:39:50AM -0400, Boruch Baum wrote:
>
> Just to clarify, and since you are talking about "default" pin levels:
> the default pin level of standard Devuan repositories is 500. The
> default for backports and experimental is 100. So I can
On 2017-07-21 14:01, KatolaZ wrote:
> On Fri, Jul 21, 2017 at 08:46:27AM -0400, Boruch Baum wrote:
> > On 2017-07-21 13:24, KatolaZ wrote:
> > > Please check this first, since dozens of people are using reportbug
> > > from jessie, and their bugs are correctly reported to bugs.devuan.org.
> >
> > E
On 2017-07-21 13:57, KatolaZ wrote:
> On Fri, Jul 21, 2017 at 08:39:50AM -0400, Boruch Baum wrote:
> > Thanks for a quick response.
> >
> >
> > On 2017-07-21 13:24, KatolaZ wrote:
> > > Which version of reportbug are you using?
> >
> > The offending version was 6.6.6~bpo8+1, and the upgraded (curre
On Fri, Jul 21, 2017 at 02:01:46PM +0100, KatolaZ wrote:
[cut]
>
> Hi,
>
> You should exercise some patience, please :) The bug reports are
> processed in batches. Your emails arrived on the server aroun 11:40,
> 11:50, 12:30 UTC time, and have been processed. You should have
> received confirm
On Fri, Jul 21, 2017 at 08:39:50AM -0400, Boruch Baum wrote:
[cut]
>
> That version does show up on my apt-cache policy output, pinned to the
> default 990 from http://auto.mirrors.devuan.org/merged jessie/main.
>
> However, version 6.6.6~bpo8+1 was likewise pinned to the default 990
> from htt
On Fri, Jul 21, 2017 at 08:46:27AM -0400, Boruch Baum wrote:
> On 2017-07-21 13:24, KatolaZ wrote:
> > Please check this first, since dozens of people are using reportbug
> > from jessie, and their bugs are correctly reported to bugs.devuan.org.
>
> Enzo, I should add that though I manually submit
On Fri, Jul 21, 2017 at 08:39:50AM -0400, Boruch Baum wrote:
> Thanks for a quick response.
>
>
> On 2017-07-21 13:24, KatolaZ wrote:
> > Which version of reportbug are you using?
>
> The offending version was 6.6.6~bpo8+1, and the upgraded (current)
> version is 7.1.6+devuan2.1.
So it was not
On 2017-07-21 13:24, KatolaZ wrote:
> Please check this first, since dozens of people are using reportbug
> from jessie, and their bugs are correctly reported to bugs.devuan.org.
Enzo, I should add that though I manually submitted THREE bug reports to
devuan this morning, I have received neither c
Thanks for a quick response.
On 2017-07-21 13:24, KatolaZ wrote:
> Which version of reportbug are you using?
The offending version was 6.6.6~bpo8+1, and the upgraded (current)
version is 7.1.6+devuan2.1.
> jessie has 6.6.3+devuan1.3,
That version does show up on my apt-cache policy output, pin
On Fri, Jul 21, 2017 at 08:15:59AM -0400, Boruch Baum wrote:
>
> Earlier today, I filed a bug report against the devuan testing version
> of 'mutt', but because I was using the stable version of devuan, and the
> stable version of reportbug, the report went to debian.
>
> Now, that was incompeten
Earlier today, I filed a bug report against the devuan testing version
of 'mutt', but because I was using the stable version of devuan, and the
stable version of reportbug, the report went to debian.
Now, that was incompetent. Was it incompetent of me or of devuan or
both?
Updating a recipient e
On Mon, Jul 10, 2017 at 07:34:02PM -0300, Douglas Guptill wrote:
> Hi all:
>
> I have worn out the previous subject of this thread; so am starting a
> new one.
>
> Thanks for the welcoming, and tolerant, reponses. In the past I have
> always worked by myself; joining a collaborative project will
Hi all:
I have worn out the previous subject of this thread; so am starting a
new one.
Thanks for the welcoming, and tolerant, reponses. In the past I have
always worked by myself; joining a collaborative project will be a
culture shock, or at least a major adjustment, for me.
I have poked arou
On Tue, Jun 20, 2017 at 07:33:30AM +0200, Arnt Karlsen wrote:
[cut]
> > depend on libsystemd0, but the dep is not harmful in Jessie, since
> > libsystemd0 does nothing if systemd is not running as pid1.
>
> ..how do we know libsystemd0 "does nothing", if we know?
>
Like "by reading the code"?
On Mon, 24 Apr 2017 19:36:11 +0100, KatolaZ wrote in message
<20170424183611.gv14...@katolaz.homeunix.net>:
> Hi Greg,
>
> thanks for your patience. Your issue was already in bugs.devuan.org
> (since the 24th March):
>
> https://bugs.devuan.org/db/31/31.html
>
> and has been closed on April
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 meeti
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 m
* 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 bugs.devuan.
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
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
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 in
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
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 major versions ago and
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 li
>
>
> --
>
> Message: 6
> Date: Sun, 14 May 2017 10:10:19 -0400
> From: fsmithred
> To: dng@lists.dyne.org
> Subject: Re: [DNG] reportbug default bts
> Message-ID:
> Content-Type: text/plain; charset=utf-8
>
> On 05/13/2017 11:
-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 buddy from my LUG whose machine
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 wondering about this myth th
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 that is not consi
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 practice.
>
> I
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 you
Le 14/05/2017 à 08:23, KatolaZ a écrit :
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
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 a
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 br
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 never dist-upgrade
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.
--
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 -v
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 usually upgrade or
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 not considered
> >
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, it breaks things.
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
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
> > |
> > Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/tri
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
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Tri
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 n
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:
>
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.
On Mon, Apr 24, 2017 at 07:36:11PM +0100, KatolaZ wrote:
> thanks for your patience. Your issue was already in bugs.devuan.org
> (since the 24th March):
Thanks KatolaZ for pointing it out. That also explains why searching
against apt-cacher-ng didn't come back with any results.
Greg
--
web sit
On Mon, Apr 24, 2017 at 10:56:04AM -0700, Gregory Nowak wrote:
> On Sun, Apr 23, 2017 at 10:09:39PM +0100, KatolaZ wrote:
> > all the known outstanding issues which were not just bare comments
> > have been already imported in bugs.devuan.org (and most of them have
> > also been fixed and closed).
On Sun, Apr 23, 2017 at 10:09:39PM +0100, KatolaZ wrote:
> all the known outstanding issues which were not just bare comments
> have been already imported in bugs.devuan.org (and most of them have
> also been fixed and closed).
Here's one example why I asked about this. I filed an issue on gitlab
On Sun, Apr 23, 2017 at 01:34:13PM -0700, Gregory Nowak wrote:
[cut]
>
> Yes, sending a bug report does indeed seem to work.
>
> I have a question though. What about the bug reports filed in gitlab?
> Will they be merged into bugs.devuan.org? Thanks.
>
Hi Greg,
all the known outstanding issu
On Sun, Apr 23, 2017 at 12:48:22AM +0100, KatolaZ wrote:
> It has been
> slightly modified to allow sending bug reports to bugs.devuan.org, but
> it still lacks some of the functionalities, e.g. looking for existing
> reports. In your case, I guess reportbug is trying to retrieve the
> reports for
On Sat, Apr 22, 2017 at 04:38:06PM -0700, Gregory Nowak wrote:
> Hi all,
> I'm trying to run reportbug, and it tells me it can't connect to
> devuan bts. I can connect to it just fine from the machine in question
> using lynx over http and https. When I run tcpdump while
> running reportbug, I see
Hi all,
I'm trying to run reportbug, and it tells me it can't connect to
devuan bts. I can connect to it just fine from the machine in question
using lynx over http and https. When I run tcpdump while
running reportbug, I see it's trying to connect to dyne.servus.at over
https. When I try to connec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Am Mo den 28. Nov 2016 um 16:40 schrieb Jaromil:
> On Sun, 27 Nov 2016, Klaus Ethgen wrote:
> > is there any plan to get reportbug working in devuan too? It is one of
> > the thinks I liked debian more than other distributions that using
> > hor
dear Klaus,
On Sun, 27 Nov 2016, Klaus Ethgen wrote:
> is there any plan to get reportbug working in devuan too? It is one of
> the thinks I liked debian more than other distributions that using
> horrible bugzilla or even worse, launchpad.
while we are using gitlab' issues for now, there has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Folks (again ;-),
is there any plan to get reportbug working in devuan too? It is one of
the thinks I liked debian more than other distributions that using
horrible bugzilla or even worse, launchpad.
Regards
Klaus
- --
Klaus Ethgen
70 matches
Mail list logo
