Bug 10547 - ttb teletext browser is broken
Summary: ttb teletext browser is broken
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Marja Van Waes
QA Contact:
URL: http://code.google.com/p/ttx-teletext/
Whiteboard: apprentice
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-16 23:42 CEST by Marja Van Waes
Modified: 2014-08-19 14:53 CEST (History)
4 users (show)

See Also:
Source RPM: ttb, ttx
CVE:
Status comment:


Attachments
ttx.spec (934 bytes, text/plain)
2013-07-19 12:04 CEST, Marja Van Waes
Details
newer version (github) ttx.spec (1002 bytes, text/plain)
2013-07-21 22:23 CEST, Marja Van Waes
Details
ttx.spec for github source (987 bytes, text/plain)
2013-10-04 20:41 CEST, Marja Van Waes
Details

Description Marja Van Waes 2013-06-16 23:42:03 CEST
ttb is broken because the Dutch NOS changed its interface.

Upstream fixed the problem with new software, ttx, which replaces ttb and which additionally works with Belgian, Austrian, German, Croatian, Portuguese, Finnish and Italian teletext services

A working spec file can be found here
http://waesvanm.home.xs4all.nl/Packaging/ttx.spec

"# Buildrequires:	pkgconfig(libxml-2.0)" will be removed, and I still need to figure out whether 
"%files -f %{name}.lang" is any use (copied it from another spec file)
Comment 1 Jani Välimaa 2013-06-19 22:08:34 CEST
%{name}.lang is the output file of '%find_lang %{name}'. If %find_lang macro is used/needed, then you also need '-f %{name}.lang'.
Comment 2 Marja Van Waes 2013-06-20 11:27:34 CEST
(In reply to Jani Välimaa from comment #1)
> %{name}.lang is the output file of '%find_lang %{name}'. If %find_lang macro
> is used/needed, then you also need '-f %{name}.lang'.

Thx, Jani :)

So it is needed.

There is something else I don't understand. When I checked (on a minimal install) what the "real" BuildRequires were, gettext was not needed.
However, I added it later, because of what our wiki says
https://wiki.mageia.org/en/Packaging_guidelines#Handling_Locale_Files

Is the wiki wrong?

When I installed bm, gettext-0.18.2.1-1.mga4 was pulled in:
http://waesvanm.home.xs4all.nl/Packaging/installing_bm.txt

Does that mean it is already on the BuildServer, too, and that it *never* needs to be added as BuildRequire?
Comment 3 Marja Van Waes 2013-06-22 20:01:56 CEST
malo just told me that the BS doesn't use bm

He checked what is already present, by submitting null without any BuildRequires http://pkgsubmit.mageia.org/uploads/done/cauldron/nonfree/release/20130622174228.malo.valstar.30112/null-10-2.mga4.nonfree/rpm_qa.0.20130622174305.log

gettext is in it, so I can remove it from the .spec
Comment 4 Marja Van Waes 2013-07-19 12:04:35 CEST
Created attachment 4211 [details]
ttx.spec

Giving up on trying to making a package directly from git (which fixes the fonttools conflict)

Could someone (if the .spec is good enough), please commit and push ttx-0.0.2 ?
Comment 5 Marja Van Waes 2013-07-19 12:05:47 CEST
about

CC: (none) => pierre-malo.denielou
Whiteboard: (none) => apprentice

Comment 6 Marja Van Waes 2013-07-21 22:23:09 CEST
Created attachment 4215 [details]
newer version (github) ttx.spec

(In reply to Marja van Waes from comment #4)

> 
> Giving up on trying to making a package directly from git (which fixes the
> fonttools conflict)
> 

Maybe I was too fast to give up.
The github ttx.spec already built fine, thanks to the precious help of coling and pterjan in Brussels
I thought the generated package wouldn't install, but just now it installed fine. The only problem is with executing, it gives the following error:

(ttx-gtk:8768): GLib-GIO-ERROR **: Settings schema 'nl.djcbsoftware.ttx' is not installed

I'll attach the github ttx.spec. A src.rpm can be found here:
http://waesvanm.home.xs4all.nl/Packaging/ttx-0.0.3-1.20130608_github_7891e954f2.mga4.src.rpm
Comment 7 Marja Van Waes 2013-10-04 20:41:40 CEST
Created attachment 4406 [details]
ttx.spec for github source

tried again last weekend

djcb (upstream) says the git source is a lot better than version 0.0.2, so I'll try to get a working package from the github source

I don't manage yet to let it build, the log.ttx can be found here
http://waesvanm.home.xs4all.nl/Packaging/github_ttx/log.ttx

There are some errors and warnings at the end (Am I correct to think only the errors can lead to a failing build, but the warnings don't?):

*******************************************************************************

ttx-window.c:413:2: warning: âgtk_tool_button_new_from_stockâ is deprecated (declared at /usr/include/gtk-3.0/gtk/gtktoolbutton.h:73): Use 'gtk_tool_button_new' instead [-Wdeprecated-declarations]
  btn = gtk_tool_button_new_from_stock (GTK_STOCK_GO_BACK);
  ^
ttx-window.c:413:40: error: âGTK_STOCK_GO_BACKâ undeclared (first use in this function)
  btn = gtk_tool_button_new_from_stock (GTK_STOCK_GO_BACK);
                                        ^
ttx-window.c:413:40: note: each undeclared identifier is reported only once for each function it appears in
ttx-window.c:424:2: warning: âgtk_tool_button_new_from_stockâ is deprecated (declared at /usr/include/gtk-3.0/gtk/gtktoolbutton.h:73): Use 'gtk_tool_button_new' instead [-Wdeprecated-declarations]
  btn = gtk_tool_button_new_from_stock (GTK_STOCK_GO_FORWARD);
  ^
ttx-window.c:424:40: error: âGTK_STOCK_GO_FORWARDâ undeclared (first use in this function)
  btn = gtk_tool_button_new_from_stock (GTK_STOCK_GO_FORWARD);
                                        ^
ttx-window.c:432:2: warning: âgtk_tool_button_new_from_stockâ is deprecated (declared at /usr/include/gtk-3.0/gtk/gtktoolbutton.h:73): Use 'gtk_tool_button_new' instead [-Wdeprecated-declarations]
  btn = gtk_tool_button_new_from_stock (GTK_STOCK_REFRESH);
  ^
ttx-window.c:432:40: error: âGTK_STOCK_REFRESHâ undeclared (first use in this function)
  btn = gtk_tool_button_new_from_stock (GTK_STOCK_REFRESH);
                                        ^
make[3]: *** [ttx-window.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory `/home/user/ttxgitNieuw/BUILD/ttx-master/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/user/ttxgitNieuw/BUILD/ttx-master/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/user/ttxgitNieuw/BUILD/ttx-master'
make: *** [all] Error 2
error: Bad exit status from /home/user/ttxgitNieuw/BUILDROOT/rpm-tmp.jsX4aa (%build)


RPM build errors:
    Bad exit status from /home/user/ttxgitNieuw/BUILDROOT/rpm-tmp.jsX4aa (%build)

**************************************************************************

Attachment 4215 is obsolete: 0 => 1

Marja Van Waes 2013-12-18 19:35:17 CET

Attachment 4211 is obsolete: 0 => 1

Comment 8 Marja Van Waes 2013-12-18 19:36:39 CET
Comment on attachment 4406 [details]
ttx.spec for github source

ttx-0.0.5-1.mga4.src.rpm has just been committed, it replaces broken ttb

Attachment 4406 is obsolete: 0 => 1

Comment 9 Shlomi Fish 2013-12-19 15:11:45 CET
Hi all,

I reviewed the ttx in the repository and rpmlint is happy, there are no trailing spaces, and the .spec looks fine to me. Seems like a good job.

[SHELL]
shlomif[rpms]:$mageia/ttx$ svn info
Path: .
Working Copy Root Path: /home/shlomif/Download/unpack/Mageia/ttx
URL: svn+ssh://svn.mageia.org/svn/packages/cauldron/ttx/current
Relative URL: ^/cauldron/ttx/current
Repository Root: svn+ssh://svn.mageia.org/svn/packages
Repository UUID: 01bf705a-734c-4999-978a-dc8ab10ec44d
Revision: 558885
Node Kind: directory
Schedule: normal
Last Changed Author: marja
Last Changed Rev: 558626
Last Changed Date: 2013-12-18 20:32:20 +0200 (Wed, 18 Dec 2013)

shlomif[rpms]:$mageia/ttx$ 

[/SHELL]

Regards,

-- Shlomi Fish

CC: (none) => shlomif

Marja Van Waes 2013-12-21 10:45:16 CET

Whiteboard: apprentice => apprentice MGA3TOO

Comment 10 Marja Van Waes 2013-12-21 18:58:30 CET
fixed in cauldron

Status: NEW => ASSIGNED
Version: Cauldron => 3
Whiteboard: apprentice MGA3TOO => apprentice

Comment 11 Remco Rijnders 2014-08-19 14:53:56 CEST
Many thanks Marja, Shlomi.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.