[SOLVED] MX-17 package update request: Xfburn

[fehlix]

Hmmm...I did a bigger set of changes.

Does this version fix it?

https://drive.google.com/open?id=1FxCv9 ... 4KnDGr7WWJ

Not realy: I do not see a difference in the start screen, which is the main show stopper.

xfburn-0.5.5-stevo1.png

The upper picture is live running your version.
below the screen dump of the orignal unpatched and my pachtched version.

[entropyfoe]

Steveo,

Wow you are an expert, able to dig into the debian stuff and the translation strings.

This is what powers MX linux above and beyond many distros.
(like one earlier poster...I to am a k3b guy)
Thanks

[Stevo]

The Debian maintainers are far more expert; I'm just wading where they are Olympic-class swimmers.

OK, try this rebuild:

https://drive.google.com/open?id=1EyQmC ... gXhdAgKh96

[fehlix]

The Debian maintainers are far more expert; I'm just wading where they are Olympic-class swimmers.

OK, try this rebuild:

Looks good:

xfburn-0.5.5-try2.png

[Stevo]

The Debian maintainers are far more expert; I'm just wading where they are Olympic-class swimmers.

OK, try this rebuild:

Looks good:
xfburn-0.5.5-try2.png

OK, will send it up. I couldn't use your patch as is, since the source has no xfburn.po file, so I just made the same changes to the /po/de.po file in the source. I suppose the Debian developers all have fancy hdpi screens and don't see any problem with the widescreen version they have.

[fehlix]

OK, will send it up. I couldn't use your patch as is, since the source has no xfburn.po file, so I just made the same changes to the /po/de.po file in the source. I suppose the Debian developers all have fancy hdpi screens and don't see any problem with the widescreen version they have.

Thanks Stevo.

[MX-16_fan]

@Stevo:

(...) Does this version fix it?

https://drive.google.com/open?id=1FxCv9 ... 4KnDGr7WWJ

Thanks! Just tried it out. Takes very long to start (about 20 seconds), and unfortunately the window still has about 35% too much in width (which, however, is, as far as I remember, less too much than with the 0.5.4 version).

Before installation, Lintian complained:

W: xfburn: latest-debian-changelog-entry-without-new-version
N: 1 tag overridden (1 warning)

Lintian finished with exit status 0

What does that mean?


Greetings, Joe

[fehlix]

you need read two posts further down
+++
EDIT:
and you might just install the final fixed version 0.5.5-1~mx17+1 from with MXPI:

Code: Select all

LANG=C apt policy xfburn
xfburn:
  Installed: 0.5.5-1~mx17+1
  Candidate: 0.5.5-1~mx17+1
  Version table:
 *** 0.5.5-1~mx17+1 500
        500 https://ftp.fau.de/mxlinux-packages/mx/repo stretch/main amd64 Packages
        100 /var/lib/dpkg/status
     0.5.4-1 500
        500 http://ftp.de.debian.org/debian stretch/main amd64 Packages

[MX-16_fan]

@fehlix:

you need read two posts further down
(...)

Thanks!



@Stevo:

Installs without issues and starts at a normal speed. This version resolves the window issue.

O.k. to mark this "SOLVED"? Or do you want me to wait until some more people have tested this version?

Thanks so much for this important fix! Do you have any means of reporting this to upstream?


Greetings, Joe

[Stevo]

I don't know if the other languages are affected, but the best way for German is to update the translation in the xfburn upstream source, whatever way they have set up to contribute--I think they have some git setup where the patch could be pushed up.. Debian also has a bug reporting setup, but any fixes usually just trickle down to the next release, instead of for stable users.