I can't create a bugzilla on LXDE for TW

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

I can't create a bugzilla on LXDE for TW

Carlos E. R.-2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hi.

I went to "search package" web page:

<https://software.opensuse.org/package/lxdm>

- From there I found that package is in X11:LXDE repo. I click on the OBS
link:

<https://build.opensuse.org/package/show/X11%3Alxde/lxdm>

and there on the report bug. I write the bug, and I get this error in bugzilla:


Assignee:   [hidden email] did not match anything
CC:
    [hidden email] did not match anything
    [hidden email] did not match anything
    [hidden email] did not match anything



LXDE is a main package (oss repo) in Leap, but not in TW, it is in an
extra repo. I found a bug and wanted to report it, but I can't.

What do I do next?

- --
Cheers

  Carlos E. R.
  (from 42.2 x86_64 "Malachite" at Telcontar)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAloTRCYACgkQtTMYHG2NR9XDEQCgjFCqGzQO7DDODnqsfsF9rW1G
pNcAn0ETkmVXjDleBq5XMIugbMjHzuFp
=d7Mc
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: I can't create a bugzilla on LXDE for TW

jcsl
El lunes, 20 de noviembre de 2017 22:07:43 (CET) Carlos E. R. escribi?:

> Hi.
>
> I went to "search package" web page:
>
> <https://software.opensuse.org/package/lxdm>
>
> From there I found that package is in X11:LXDE repo. I click on the OBS
> link:
>
> <https://build.opensuse.org/package/show/X11%3Alxde/lxdm>
>
> and there on the report bug. I write the bug, and I get this error in
> bugzilla:
>
>
> Assignee:   [hidden email] did not match anything
> CC:
>     [hidden email] did not match anything
>     [hidden email] did not match anything
>     [hidden email] did not match anything
>
>
>
> LXDE is a main package (oss repo) in Leap, but not in TW, it is in an
> extra repo. I found a bug and wanted to report it, but I can't.
>
> What do I do next?
>
> --
> Cheers
>
>   Carlos E. R.
>   (from 42.2 x86_64 "Malachite" at Telcontar)

Hi.

LXDM was removed from Tumbleweed sometime ago and replaced with LightDM. You
can find the reasons searching in this mailing list. If you've found a bug in
the software, then you should file the bug report to:

  https://sourceforge.net/p/lxde/bugs/

And then be patient. The development of LXDE is way slow these days. However,
when a new Debian release is near, there is a lot of changes/bug fixes
usually.

Greetings.

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: I can't create a bugzilla on LXDE for TW

Carlos E. R.-2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



El 2017-11-21 a las 19:22 +0100, jcsl escribió:

> El lunes, 20 de noviembre de 2017 22:07:43 (CET) Carlos E. R. escribi?:
>> Hi.
>>
>> I went to "search package" web page:
>>
>> <https://software.opensuse.org/package/lxdm>
>>
>> From there I found that package is in X11:LXDE repo. I click on the OBS
>> link:
>>
>> <https://build.opensuse.org/package/show/X11%3Alxde/lxdm>
>>
>> and there on the report bug. I write the bug, and I get this error in
>> bugzilla:
>>
>>
>> Assignee:   [hidden email] did not match anything
>> CC:
>>     [hidden email] did not match anything
>>     [hidden email] did not match anything
>>     [hidden email] did not match anything
>>
>>
>>
>> LXDE is a main package (oss repo) in Leap, but not in TW, it is in an
>> extra repo. I found a bug and wanted to report it, but I can't.
>>
>> What do I do next?
>>
> Hi.
>
> LXDM was removed from Tumbleweed sometime ago and replaced with LightDM. You
> can find the reasons searching in this mailing list. If you've found a bug in
> the software, then you should file the bug report to:
>
>  https://sourceforge.net/p/lxde/bugs/
>
> And then be patient. The development of LXDE is way slow these days. However,
> when a new Debian release is near, there is a lot of changes/bug fixes
> usually.
No, I want to report a bug against the openSUSE OBS package in particular,
not upstream.

The people that are configured to accept those bugs are refused by the
bugzilla system. There must be a mechanism to report these errors.

- --
Cheers
        Carlos E. R.

        (from openSUSE 42.2 x86_64 "Malachite" (Minas Tirith))
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iF4EAREIAAYFAloUdBkACgkQja8UbcUWM1xJbAD/bca4tGcvJPAhLw25RL6XBPVL
AqIdKT0keRc5fm0MACUA/j6PnJCnYw7QenXSslcs8IqGUHxK1OPDynMKFg7xnwk+
=1nSB
-----END PGP SIGNATURE-----
Reply | Threaded
Open this post in threaded view
|

Re: I can't create a bugzilla on LXDE for TW

Per Jessen
Carlos E. R. wrote:

> No, I want to report a bug against the openSUSE OBS package in
> particular, not upstream.
>
> The people that are configured to accept those bugs are refused by the
> bugzilla system. There must be a mechanism to report these errors.

You could try reporting it on the OBS mailing list, or maybe writing to
[hidden email].



--
Per Jessen, Zürich (7.5°C)
http://www.dns24.ch/ - free dynamic DNS, made in Switzerland.

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: I can't create a bugzilla on LXDE for TW

jcsl
In reply to this post by Carlos E. R.-2
El martes, 21 de noviembre de 2017 19:44:32 (CET) Carlos E. R. escribió:

> El 2017-11-21 a las 19:22 +0100, jcsl escribió:
> > El lunes, 20 de noviembre de 2017 22:07:43 (CET) Carlos E. R. escribi?:
> >> Hi.
> >>
> >> I went to "search package" web page:
> >>
> >> <https://software.opensuse.org/package/lxdm>
> >>
> >> From there I found that package is in X11:LXDE repo. I click on the OBS
> >> link:
> >>
> >> <https://build.opensuse.org/package/show/X11%3Alxde/lxdm>
> >>
> >> and there on the report bug. I write the bug, and I get this error in
> >> bugzilla:
> >>
> >>
> >> Assignee:   [hidden email] did not match anything
> >>
> >> CC:
> >>     [hidden email] did not match anything
> >>     [hidden email] did not match anything
> >>     [hidden email] did not match anything
> >>
> >> LXDE is a main package (oss repo) in Leap, but not in TW, it is in an
> >> extra repo. I found a bug and wanted to report it, but I can't.
> >>
> >> What do I do next?
> >
> > Hi.
> >
> > LXDM was removed from Tumbleweed sometime ago and replaced with LightDM.
> > You can find the reasons searching in this mailing list. If you've found
> > a bug in>
> > the software, then you should file the bug report to:
> >  https://sourceforge.net/p/lxde/bugs/
> >
> > And then be patient. The development of LXDE is way slow these days.
> > However, when a new Debian release is near, there is a lot of changes/bug
> > fixes usually.
>
> No, I want to report a bug against the openSUSE OBS package in particular,
> not upstream.
>
> The people that are configured to accept those bugs are refused by the
> bugzilla system. There must be a mechanism to report these errors.
>
> --
> Cheers
>         Carlos E. R.
>
>         (from openSUSE 42.2 x86_64 "Malachite" (Minas Tirith))

Hi.

LXDE has no active maintainers AFAIK. You can leave a comment in the package
page. It may be read by someone with access to the repository and the error
fixed... or not.

I think the error is this line in the .spec file:

sed -i 's/sbin/bin/' %{buildroot}/usr/lib/systemd/system/lxdm.service

Greetings.

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: I can't create a bugzilla on LXDE for TW

Carlos E. R.-2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Content-ID: <[hidden email]>


El 2017-11-21 a las 19:58 +0100, jcsl escribió:

> El martes, 21 de noviembre de 2017 19:44:32 (CET) Carlos E. R. escribió:
>> El 2017-11-21 a las 19:22 +0100, jcsl escribió:
>>> El lunes, 20 de noviembre de 2017 22:07:43 (CET) Carlos E. R. escribi?:


>> No, I want to report a bug against the openSUSE OBS package in particular,
>> not upstream.
>>
>> The people that are configured to accept those bugs are refused by the
>> bugzilla system. There must be a mechanism to report these errors.
>>
>
> Hi.
>
> LXDE has no active maintainers AFAIK. You can leave a comment in the package
> page. It may be read by someone with access to the repository and the error
> fixed... or not.
>
> I think the error is this line in the .spec file:
>
> sed -i 's/sbin/bin/' %{buildroot}/usr/lib/systemd/system/lxdm.service
>
> Greetings.
Thanks. But you see, I'm not using LXDE at all!  I was reporting a problem
in lightdm and somebody told me to try lxdm, and I did, out of curiosity.
I found a bug, and thought my duty to report it in the proper channel:
Bugzilla.

But if it is not maintained, my interest in LXDE is lost and I stop here.

Maybe the repository should be removed.


The problem remains, how to report a problem with the OBS-Bugzilla system
itself. A maintainer is listed. Some addresses are _automatically_ written
to the bugzilla. But Bugzilla says that those addresses are unknown!

In fact, at least one of those addresses, at novell, bounces.

There should be a written documented procedure on how to deal with this
situations.

- --
Cheers
        Carlos E. R.

        (from openSUSE 42.2 x86_64 "Malachite" (Minas Tirith))
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iF4EAREIAAYFAloUhJYACgkQja8UbcUWM1yamQEAgzdlviQPUyPRp0tJzKmNMh6e
fL5MKKr4iDOwsZIpp0gA/iXb0/Pj8Vsox5b3iKuCjAtKlclKSX2ep8XkznuqGEKB
=iB7J
-----END PGP SIGNATURE-----
Reply | Threaded
Open this post in threaded view
|

Re: I can't create a bugzilla on LXDE for TW

Carlos E. R.-2
In reply to this post by Per Jessen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256


El 2017-11-21 a las 19:52 +0100, Per Jessen escribió:

> Carlos E. R. wrote:
>
>> No, I want to report a bug against the openSUSE OBS package in
>> particular, not upstream.
>>
>> The people that are configured to accept those bugs are refused by the
>> bugzilla system. There must be a mechanism to report these errors.
>
> You could try reporting it on the OBS mailing list, or maybe writing to
> [hidden email].
Thanks.

My previous mail I forwarded to the people the OBS say are responsible.
I'll wait a bit to see if they say something, even if it is "I removed
myself from the OBS link".

Meanwhile, I have one FF tab occupied with the bug report that I can not
send. I might clear them out, send to the default bugowner for the entire
OBS, and forget.

No wonder that some people say they don't want to write a bugzilla ever again!

- --
Cheers
        Carlos E. R.

        (from openSUSE 42.2 x86_64 "Malachite" (Minas Tirith))

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iF4EAREIAAYFAloUhYIACgkQja8UbcUWM1zAnAD/QJqqaG8n0v3Zmoh+jSbe8BRi
f5pEDW3Ce5gg8p8pNeUA+QHBhT8hF30+yxagyOQy1RUHR2Bb3VF2pBC/EiYge/AR
=3o4Q
-----END PGP SIGNATURE-----
Reply | Threaded
Open this post in threaded view
|

Re: I can't create a bugzilla on LXDE for TW

Christian Boltz-5
In reply to this post by Carlos E. R.-2
Hello,

Am Dienstag, 21. November 2017, 20:55:02 CET schrieb Carlos E. R.:

> The problem remains, how to report a problem with the OBS-Bugzilla
> system itself. A maintainer is listed. Some addresses are
> _automatically_ written to the bugzilla. But Bugzilla says that those
> addresses are unknown!

I can imagine a few reasons why this happens, for example:
- someone never logged in into bugzilla, and therefore bugzilla doesn't
  know his/her mail addresss
- someone changed the mail address, and since then, only logged in in
  bugzilla _or_ OBS, so it got updated only at one place
- someone left SUSE and the bugzilla account therefore got disabled

> In fact, at least one of those addresses, at novell, bounces.
>
> There should be a written documented procedure on how to deal with
> this situations.

Feel free to read any documentation about searching for easter eggs ;-)

Seriously: If I hit such a situation, I typically check the changelog
for the last people who worked on the package. Another option is to
start typing the name in the bugzilla assignee field and wait if the
autocompletion comes up with a different mail address for that person.

I assume you know how to edit the wiki - feel free to find a nice place
for this and add it there ;-)


That said - the last change to the lxdm package was two years ago and it
was dropped from Tumbleweed, therefore I wouldn't expect too much from a
bugreport in this specific case.


Regards,

Christian Boltz
--
| $ rpm -q --whatrequires kernel
| no package requires kernel
Ach ja, dascha interessant! Kein RPM braucht das? Ja wie? Dann kann
ich das RPM ja also beruhigt loeschen? Braucht ja keiner... *lol*
[David Haller in suse-linux]

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: I can't create a bugzilla on LXDE for TW

Dave Plater lst
In reply to this post by Carlos E. R.-2


On 21/11/2017 21:55, Carlos E. R. wrote:
> The problem remains, how to report a problem with the OBS-Bugzilla
> system itself. A maintainer is listed. Some addresses are
> _automatically_ written to the bugzilla. But Bugzilla says that those
> addresses are unknown!
Report the bug and leave it unassigned, the quality control team will
take the appropriate action.
Dave P
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: I can't create a bugzilla on LXDE for TW

Richard Brown
On 22 November 2017 at 08:34, Dave Plater <[hidden email]> wrote:

>
>
> On 21/11/2017 21:55, Carlos E. R. wrote:
>>
>> The problem remains, how to report a problem with the OBS-Bugzilla system
>> itself. A maintainer is listed. Some addresses are _automatically_ written
>> to the bugzilla. But Bugzilla says that those addresses are unknown!
>
> Report the bug and leave it unassigned, the quality control team will take
> the appropriate action.
> Dave P

Not bad advice, except

a) there is no formal 'quality control team' - just some proactive
contributors who take it upon themselves to look at unassigned bugs.
This is an area we could do with some help, basically anyone who knows
how to look at a bug and use OBS/osc to figure out likely people to
fix it could help.

b) In this case Carlos is trying to file a bug against an
orphaned/dead/removed piece of software.
It is not in Tumbleweed. It should not be expected to have any active
contributions going forward.

This should be a good reminder that devel projects are not supported
projects, and there should be no expectation that packages in devel
projects have any kind of support or contributions.

This is a perfect example why I bleat on about that so often - there
is no active maintenance of lxdm, so there is no one to report the bug
to.

The only thing we could perhaps improve here is making it a little
clearer that no matter what workarounds we could apply to get a bug
filed in OBS, an lxdm bug report might as well go to /dev/null
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: I can't create a bugzilla on LXDE for TW

Michael Vetter
In reply to this post by Carlos E. R.-2
Hi Carlos,

Sorry to hear about your troubles ;)

On Mon, 20 Nov 2017 22:07:43 +0100 (CET)
"Carlos E. R." <[hidden email]> wrote:

> - From there I found that package is in X11:LXDE repo. I click on the
> OBS link:
>
> <https://build.opensuse.org/package/show/X11%3Alxde/lxdm>
>
> and there on the report bug. I write the bug, and I get this error in
> bugzilla:
>
>
> Assignee:   [hidden email] did not match anything
> CC:
>     [hidden email] did not match anything
>     [hidden email] did not match anything
>     [hidden email] did not match anything

This surprised me, because my private mail ([hidden email]) is right.

>- someone changed the mail address, and since then, only logged in in
>  bugzilla _or_ OBS, so it got updated only at one place

This explains it however ;-)

> LXDE is a main package (oss repo) in Leap, but not in TW, it is in an
> extra repo. I found a bug and wanted to report it, but I can't.
LXDE doesnt' have any active maintainers in openSUSE.
Although upstream became a little more active some months ago its still
very slow.

For historical reasons I have rights to LXDE devel proj and
answer/review requests there but do not proactively do much about LXDE.

Michael
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: I can't create a bugzilla on LXDE for TW

Carlos E. R.-2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On Thursday, 2017-11-23 at 12:09 +0100, Michael Vetter wrote:

> Hi Carlos,
>
> Sorry to hear about your troubles ;)
>
> On Mon, 20 Nov 2017 22:07:43 +0100 (CET)
> "Carlos E. R." <[hidden email]> wrote:
>> - From there I found that package is in X11:LXDE repo. I click on the
>> OBS link:
>>
>> <https://build.opensuse.org/package/show/X11%3Alxde/lxdm>
>>
>> and there on the report bug. I write the bug, and I get this error in
>> bugzilla:
>>
>>
>> Assignee:   [hidden email] did not match anything
>> CC:
>>     [hidden email] did not match anything
>>     [hidden email] did not match anything
>>     [hidden email] did not match anything
>
> This surprised me, because my private mail ([hidden email]) is right.
>
>> - someone changed the mail address, and since then, only logged in in
>>  bugzilla _or_ OBS, so it got updated only at one place
>
> This explains it however ;-)

Ah.

>
>> LXDE is a main package (oss repo) in Leap, but not in TW, it is in an
>> extra repo. I found a bug and wanted to report it, but I can't.
> LXDE doesnt' have any active maintainers in openSUSE.
> Although upstream became a little more active some months ago its still
> very slow.
>
> For historical reasons I have rights to LXDE devel proj and
> answer/review requests there but do not proactively do much about LXDE.


Well, if OBS:X11:LXDE have no maintainers on TW, I think the repo should
be removed or disabled to avoid confussions. As TW evolves, the distance
will get bigger and bigger.

As I said elsewhere, I don't use LXDE myself, I simply bumped into a
problem while testing for something else, so I thought I would report it.

- --
Cheers,
        Carlos E. R.
        (from openSUSE 42.2 x86_64 "Malachite" at Telcontar)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAloXHQMACgkQtTMYHG2NR9VH8QCeK3xDVZ83A//GRRhT5gQXseZ3
N3EAoJV6KW9MznhhCUaMQ78ZIi1Oyp46
=ZojL
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: I can't create a bugzilla on LXDE for TW

Carlos E. R.-2
In reply to this post by Richard Brown
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On Wednesday, 2017-11-22 at 16:01 +0100, Richard Brown wrote:

> On 22 November 2017 at 08:34, Dave Plater <[hidden email]> wrote:
>>
>>
>> On 21/11/2017 21:55, Carlos E. R. wrote:
>>>
>>> The problem remains, how to report a problem with the OBS-Bugzilla system
>>> itself. A maintainer is listed. Some addresses are _automatically_ written
>>> to the bugzilla. But Bugzilla says that those addresses are unknown!
>>
>> Report the bug and leave it unassigned, the quality control team will take
>> the appropriate action.
>> Dave P

This is what I will do, because I don't know what else I can do.

> Not bad advice, except
>
> a) there is no formal 'quality control team' - just some proactive
> contributors who take it upon themselves to look at unassigned bugs.
> This is an area we could do with some help, basically anyone who knows
> how to look at a bug and use OBS/osc to figure out likely people to
> fix it could help.
>
> b) In this case Carlos is trying to file a bug against an
> orphaned/dead/removed piece of software.
> It is not in Tumbleweed. It should not be expected to have any active
> contributions going forward.

It is in the OBS, and the OBS has a "report bug" link. I simply used that
link and expected it to work.

It does not matter if it is fully part of TW or not.


As I explained elsewhere, I don't use LXDE. I was testing something else,
bumped into a bug, and though my duty to report it. Simple as that.


- --
Cheers,
        Carlos E. R.
        (from openSUSE 42.2 x86_64 "Malachite" at Telcontar)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAloXHd0ACgkQtTMYHG2NR9UNqACgjp+uGDq8aIlazulClGjfwfEP
RtAAn3hA1K0z0ZIlLedKPQeVwlIqFm6e
=cbjF
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]