Re: Bringing back rsibreak from unmaintained

2015-09-07 Thread Albert Astals Cid
El Diumenge, 30 d'agost de 2015, a les 18:50:12, Jeremy Whiting va escriure: > Just rebuilt it. It seems to run ok. The config dialog does look a lot > cleaner. nice work. I'll report back if I hit any issues as it runs > and such. Since there's been no complains i'll ask for it to be moved to

Re: Bringing back rsibreak from unmaintained

2015-08-30 Thread Jeremy Whiting
Just rebuilt it. It seems to run ok. The config dialog does look a lot cleaner. nice work. I'll report back if I hit any issues as it runs and such. On Sun, Aug 30, 2015 at 4:10 PM, Albert Astals Cid aa...@kde.org wrote: El Dimecres, 19 d'agost de 2015, a les 01:01:35, Jan Kundrát va escriure:

Re: Bringing back rsibreak from unmaintained

2015-08-18 Thread Jan Kundrát
On Monday, 17 August 2015 20:04:04 CEST, Albert Astals Cid wrote: Other comments? Nice, happy to see it -- it builds here, with a bunch of warnings: [2/29] Generating index.cache.bz2 index.docbook:2: element para: validity error : ID gnu-fdl already defined element div: validity error : ID

Re: Bringing back rsibreak from unmaintained

2015-08-18 Thread Albert Astals Cid
El Dimarts, 18 d'agost de 2015, a les 19:06:22, Jan Kundrát va escriure: On Monday, 17 August 2015 20:04:04 CEST, Albert Astals Cid wrote: Other comments? Nice, happy to see it -- it builds here, with a bunch of warnings: [2/29] Generating index.cache.bz2 index.docbook:2: element para:

Re: Bringing back rsibreak from unmaintained

2015-08-18 Thread Luigi Toscano
Jan Kundrát ha scritto: On Monday, 17 August 2015 20:04:04 CEST, Albert Astals Cid wrote: Other comments? Nice, happy to see it -- it builds here, with a bunch of warnings: [2/29] Generating index.cache.bz2 index.docbook:2: element para: validity error : ID gnu-fdl already defined

Re: Bringing back rsibreak from unmaintained

2015-08-18 Thread Albert Astals Cid
El Dimecres, 19 d'agost de 2015, a les 01:00:13, Christoph Feck va escriure: On Monday 17 August 2015 20:04:04 Albert Astals Cid wrote: Hi guys, i just merged the frameworks port of rsibreak to master. rsibreak is in the unmaintained silo, i'd like to bring it back to extragear- utils (i

Re: Bringing back rsibreak from unmaintained

2015-08-18 Thread Jeremy Whiting
That surprises me. It worked fine here as I've been testing it with everything else built on master. On Tue, Aug 18, 2015 at 4:30 PM, Albert Astals Cid aa...@kde.org wrote: El Dimarts, 18 d'agost de 2015, a les 19:06:22, Jan Kundrát va escriure: On Monday, 17 August 2015 20:04:04 CEST, Albert

Re: Bringing back rsibreak from unmaintained

2015-08-18 Thread Christoph Feck
On Monday 17 August 2015 20:04:04 Albert Astals Cid wrote: Hi guys, i just merged the frameworks port of rsibreak to master. rsibreak is in the unmaintained silo, i'd like to bring it back to extragear- utils (i guess kdeutils is too much for this niche app?). Anyone wants to review it?

Re: Bringing back rsibreak from unmaintained

2015-08-18 Thread Jan Kundrát
On Wednesday, 19 August 2015 01:00:13 CEST, Christoph Feck wrote: -- Build files have been written to: /local/build/kf5/rsibreak /local/git/extragear/utils/rsibreak/src/rsitimer.cpp:26:20: fatal error: kdebug.h: No such file or directory A missing dep on kde4libssupport,

Re: Bringing back rsibreak from unmaintained

2015-08-18 Thread Jan Kundrát
On Wednesday, 19 August 2015 00:30:01 CEST, Albert Astals Cid wrote: These messages are not new, IMHO does not apply to this request of bringing back from unmaintiained ;) I agree that it's not a blocker of course, but you asked for feedback :). However, the worst thing is that the passive

Re: Bringing back rsibreak from unmaintained

2015-08-17 Thread Jeremy Whiting
Builds and runs fine here. I say +1 On Mon, Aug 17, 2015 at 12:04 PM, Albert Astals Cid aa...@kde.org wrote: Hi guys, i just merged the frameworks port of rsibreak to master. rsibreak is in the unmaintained silo, i'd like to bring it back to extragear- utils (i guess kdeutils is too much for