Dear Devuaners,
just to let you know that the Devuan's bug tracking system is finally
available online at:
https://bugs.devuan.org
The system is compatible with the BTS used by Debian (we are actually
using the same code base), and shares the same workflow. We must thank
golinux for the fantas
On Mon, 3 Apr 2017 13:58:12 +0100, KatolaZ wrote in message
<20170403125812.gs7...@katolaz.homeunix.net>:
> Dear Devuaners,
>
> just to let you know that the Devuan's bug tracking system is finally
> available online at:
>
> https://bugs.devuan.org
>
> The system is compatible with the BTS u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Am Mo den 3. Apr 2017 um 13:58 schrieb KatolaZ:
> just to let you know that the Devuan's bug tracking system is finally
> available online at:
>
> https://bugs.devuan.org
>
> The system is compatible with the BTS used by Debian (we are actu
On Mon, Apr 03, 2017 at 05:01:58PM +0100, Klaus Ethgen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hi,
>
> Am Mo den 3. Apr 2017 um 13:58 schrieb KatolaZ:
> > just to let you know that the Devuan's bug tracking system is finally
> > available online at:
> >
> > https://bugs
On Mon, Apr 03, 2017 at 05:24:26PM +0200, Arnt Karlsen wrote:
[cut]
> >
> > Please use both tools as much as possible and report any bugs to
> > bugs.devuan.org ;)
> >
> > HH
> >
> > KatolaZ
> >
>
> ..can the tricks in https://bugs.devuan.org/Developer.html be
> used by non-devuan dev peopl
Hi,
Doesn't seems to work. The mail (see attachment) went out but no bug is opened.
2017-04-03 21:53:05 1cv82D-0004E2-4w <= kl...@ethgen.de H=(ikki.ket)
[192.168.17.4] P=esmtpsa X=TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256 CV=no
A=plain_server:ikki S=3678 id=20170403195304.e2srg6biwapru...@ikki.
On Mon, 3 Apr 2017 16:43:01 +0100, KatolaZ wrote in message
<20170403154301.gy7...@katolaz.homeunix.net>:
> On Mon, Apr 03, 2017 at 05:24:26PM +0200, Arnt Karlsen wrote:
>
> [cut]
>
> > >
> > > Please use both tools as much as possible and report any bugs to
> > > bugs.devuan.org ;)
> > >
> >
On Mon, Apr 03, 2017 at 09:01:37PM +0100, Klaus Ethgen wrote:
> Hi,
>
> Doesn't seems to work. The mail (see attachment) went out but no bug is
> opened.
>2017-04-03 21:53:05 1cv82D-0004E2-4w <= kl...@ethgen.de H=(ikki.ket)
> [192.168.17.4] P=esmtpsa X=TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Am Mo den 3. Apr 2017 um 21:26 schrieb KatolaZ:
> you should just be patient.
Yes, this is my "Bug". ;-)
> Incoming bugs are processed by a cron script, and the web pages are
> updated at a slower pace.
Ah, ok, thought it is processed by MTA
On Mon, Apr 03, 2017 at 09:40:52PM +0100, Klaus Ethgen wrote:
[cut]
>
> > You should have already received a confirmation email from the BTS
> > saying that the bug has been received and processed.
>
> Yes. However, it didn't process my Severity.
>
That's a problem with reportbug, since the l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Am Mo den 3. Apr 2017 um 21:46 schrieb KatolaZ:
> > Yes. However, it didn't process my Severity.
> That's a problem with reportbug, since the list of severities does not
> match those configured in the BTS. It's my fault. I will now open a
> bu
On Mon, Apr 03, 2017 at 10:10:29PM +0100, Klaus Ethgen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hi,
>
> Am Mo den 3. Apr 2017 um 21:46 schrieb KatolaZ:
> > > Yes. However, it didn't process my Severity.
> > That's a problem with reportbug, since the list of severities does
12 matches
Mail list logo
