Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #160796 > unrolled thread

Should I report this bug with reportbug?

Back to article view | Back to linux.debian.user

Contents

  Should I report this bug with reportbug? David Cimadevilla <david@cimaware.com> - 2015-11-19 13:40 +0100
    Re: Should I report this bug with reportbug? Darac Marjal <mailinglist@darac.org.uk> - 2015-11-19 14:30 +0100

#160796 — Should I report this bug with reportbug?

I have installed solydk, a debian jessie based distro. In the latest 
update one of the installed packages messed up all my kde/qt apps.

This package comes from debian jessie security updates repository. 
Installing the previous version of the package the issue goes away.

Since extrictily I am not a debian user, should I report this bug with 
reportbug?

These are my repos:

            deb http://repository.solydxk.com solydxk main upstream import
            deb http://ftp.debian.org/debian jessie main contrib non-free
            deb http://security.debian.org jessie/updates main contrib 
non-free
            deb http://ftp.debian.org/debian jessie-backports main 
contrib non-free

[toc] | [next] | [standalone]

#160800

[Multipart message — attachments visible in raw view] — view raw

On Thu, Nov 19, 2015 at 01:16:58PM +0100, David Cimadevilla wrote:

>I have installed solydk, a debian jessie based distro. In the latest 
>update one of the installed packages messed up all my kde/qt apps.
>
>This package comes from debian jessie security updates repository. 
>Installing the previous version of the package the issue goes away.
>
>Since extrictily I am not a debian user, should I report this bug with 
>reportbug?

Ideally, yes.

If Solydk is a derivative of debian, then good practice says that it 
should maintain its own bugtracker and configure reportbug to send bug 
reports there. If the Solydk developers determine that the bug is NOT 
due to their modifications, they can opt to forward the bug to their 
"upstream" project (i.e. Debian) or perhaps to the originator of the 
package (i.e. the original developer).

You should check the configuration of reportbug, though. If you're 
running Solydk, you're not running Debian, so the bug may well not be 
relevant to Debian.

>
>These are my repos:
>
>           deb http://repository.solydxk.com solydxk main upstream 
>import deb http://ftp.debian.org/debian jessie main contrib non-free 
>deb http://security.debian.org jessie/updates main contrib non-free deb 
>http://ftp.debian.org/debian jessie-backports main contrib non-free
>

Is this the accepted configuration for Solydk, or have you added 
Debian's repositories yourself? This seems like a recipe for trouble to 
me. Solydk has, presumably, made modifications to packages - at the very 
least, adding their own branding. If you then pull in a debian package 
as a "security update", it won't honour those modifications and there is 
a definite risk of breaking the system.

-- For more information, please reread.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web