Bug#881719: libcdio 2.1.0 and lubcdio++

2020-07-26 Thread Vasyl Gello
Hi Gabriel! Let me explain more briefly how I see the future of Kodi from Debian according to my grand plan. July 26, 2020 4:33:22 PM UTC, "Gabriel F. T. Gomes" написав(-ла): >Hmm, that's not a decision to be made lightly. Would the backport to >buster fix any bugs or add features that users

Bug#881719: libcdio 2.1.0 and lubcdio++

2020-07-26 Thread Gabriel F. T. Gomes
Hi, Vasyl, On 26 Jul 2020, Vasyl Gello wrote: >I need it to satisfy kodi build dependency in libcdio++. Actually, when Kodi >19.0 goes live officially, >I would like to have it in unstable, testing (if it gets released before the >freeze takes place) That sounds reasonable, and I'm already

Bug#881719: libcdio 2.1.0 and lubcdio++

2020-07-25 Thread Vasyl Gello
Hi Gabriel! July 25, 2020 11:11:05 PM UTC, "Gabriel F. T. Gomes" написав(-ла): >On 25 Jul 2020, Vasyl Gello wrote: >>Without that, we can not upload backport to buster-bpo. > >I'm sorry if you have mentioned this before, but why is a backport >needed? I need it to satisfy kodi build dependency

Bug#881719: libcdio 2.1.0 and lubcdio++

2020-07-25 Thread Gabriel F. T. Gomes
Hi, Vasyl, On 25 Jul 2020, Vasyl Gello wrote: > >Can you please upload libcdio to unstable? Yes. The upload to experimental didn't help *me* much with the testing of pragha, because, in order for pragha to use the new version, I also had to rebuild (locally) libcdio-paranoia (if I install

Bug#881719: libcdio 2.1.0 and lubcdio++

2020-07-25 Thread Vasyl Gello
Hi Gabriel! Can you please upload libcdio to unstable? Without that, we can not upload backport to buster-bpo. --  Vasyl Gello == Certified SolidWorks Expert Mob.:+380 (98) 465 66 77 E-Mail: vasek.ge...@gmail.com Skype: vasek.gello

Bug#881719: libcdio 2.1.0 and lubcdio++

2020-07-10 Thread Mattia Rizzolo
On Fri, Jul 10, 2020 at 06:53:33AM +, Vasyl Gello wrote: > Hi Gabriel! > > I investigated the reprotest failure on libcdio and it seems a reborn > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795690 > Is it possible to exclude GMT-14 from reprotest or is it better to try fixing >

Bug#881719: libcdio 2.1.0 and lubcdio++

2020-07-10 Thread Vasyl Gello
Hi Gabriel! I investigated the reprotest failure on libcdio and it seems a reborn https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795690 Is it possible to exclude GMT-14 from reprotest or is it better to try fixing upstream instead? --  Vasyl Gello

Bug#881719: libcdio 2.1.0 and lubcdio++

2020-06-29 Thread Gabriel F. T. Gomes
Hi, Vasyl, On Mon, 29 Jun 2020, Vasyl Gello wrote: > The MR I amended after Gabriel's review is stuck since June 2nd. Yes, my bad. > Gabriel, can you please revise the MR and upload the fixed package to the > queue? Will do (I'll try to do it today)! Thanks for the heads-up. :)

Bug#881719: libcdio 2.1.0 and lubcdio++

2020-06-29 Thread Vasyl Gello
Dear colleagues, The MR I amended after Gabriel's review is stuck since June 2nd. Gabriel, can you please revise the MR and upload the fixed package to the queue? --  Vasyl Gello == Certified SolidWorks Expert Mob.:+380 (98) 465 66 77 E-Mail: 

Bug#881719: libcdio 2.1.0 and lubcdio++

2020-06-02 Thread Vasyl Gello
Hi Gabriel, Balint! Please check merge request to debian/cdio. Reprotest still fails at a first glance, but lintian warnings have gone. I will try fixing it but I need to install reprotest hook inside my pbuilder. If you manage to fix reprotest, please let me know. --  Vasyl Gello

Bug#881719: libcdio 2.1.0 and lubcdio++

2020-06-02 Thread Gabriel F. T. Gomes
On Tue, 02 Jun 2020, Bálint Réczey wrote: > > Done. I've omitted the last commit because I suggest using -1~exp0 > Debian version for the upload to experimental. IMO looks nicer when > the upload to unstable has -1. Thanks for the review. I'll fix this, then upload again to mentors.

Bug#881719: libcdio 2.1.0 and lubcdio++

2020-06-02 Thread Bálint Réczey
Hi Gabriel, Gabriel F. T. Gomes ezt írta (időpont: 2020. jún. 2., K, 0:46): > > On 01 Jun 2020, Bálint Réczey wrote: > > > >I've checked the package and it refers to > >https://salsa.debian.org/debian/libcdio as the packaging repo while it > >is not present. > >I fyou agree let me clone your

Bug#881719: libcdio 2.1.0 and lubcdio++

2020-06-01 Thread Gabriel F. T. Gomes
On 01 Jun 2020, Bálint Réczey wrote: > >I've checked the package and it refers to >https://salsa.debian.org/debian/libcdio as the packaging repo while it >is not present. >I fyou agree let me clone your packaging repo there, then I can review >the changes. Oh, please. And thank you. :) >I can't

Bug#881719: libcdio 2.1.0 and lubcdio++

2020-06-01 Thread Vasyl Gello
Hi Gabriel! I have just checked the mentors page for libcdio & found out Lintian is mad about some issues. Let me fix it quickly and file a new PR. Vasyl On Mon, 1 Jun 2020 13:23:48 +0200 =?UTF-8?B?QsOhbGludCBSw6ljemV5?= wrote: > Hi Gabriel, > > Vasyl Gello ezt írta (időpont: 2020. jún.

Bug#881719: libcdio 2.1.0 and lubcdio++

2020-06-01 Thread Bálint Réczey
Hi Gabriel, Vasyl Gello ezt írta (időpont: 2020. jún. 1., H, 7:49): > > Hi Gabriel! > > >The package is now on mentors: > > > >https://mentors.debian.net/package/libcdio I've checked the package and it refers to https://salsa.debian.org/debian/libcdio as the packaging repo while it is not

Bug#881719: libcdio 2.1.0 and lubcdio++

2020-05-31 Thread Vasyl Gello
Hi Gabriel! >The package is now on mentors: > >https://mentors.debian.net/package/libcdio > >Balint, could you review it and, if everything is fine, sponsor it? >(I'm asking because Vasyl mentioned you are guiding the packaging of >Kodi, if I got it right) Yes, you are correct. I also did upload

Bug#881719: libcdio 2.1.0 and lubcdio++

2020-05-31 Thread Gabriel F. T. Gomes
On 31 May 2020, Gabriel F. T. Gomes wrote: > >we will need a sponsor. The package is now on mentors: https://mentors.debian.net/package/libcdio Balint, could you review it and, if everything is fine, sponsor it? (I'm asking because Vasyl mentioned you are guiding the packaging of Kodi, if I got

Bug#881719: libcdio 2.1.0 and lubcdio++

2020-05-31 Thread Gabriel F. T. Gomes
Hi, Vasyl, On 24 May 2020, Vasyl Gello wrote: > >Yes experimental is OK for me, even though I uploaded libshairplay & >libudfread to unstable queue. Balint asked me initially to target Kodi 19.0 to >experimental so I will probably re-upload both libraries to experimental to >keep everything

Bug#881719: libcdio 2.1.0 and lubcdio++

2020-05-24 Thread Vasyl Gello
Hi Gabriel! May 24, 2020 9:40:59 PM UTC, "Gabriel F. T. Gomes" написав(-ла): > >Initially, and because I was a little >uncomfortable with the soname change, I thought about uploading to >experimental first. Would that work for you? > Yes experimental is OK for me, even though I uploaded

Bug#881719: libcdio 2.1.0 and lubcdio++

2020-05-24 Thread Gabriel F. T. Gomes
Hi, Vasyl, on 24 May 2020, Vasyl Gello wrote: > >Gabriel has prepared 2.1.0 in his Salsa repo and I added C++ interfaces needed >by Kodi 19.0: >https://salsa.debian.org/gabrielftg-guest/libcdio/-/merge_requests/1 Thank you so much for writing this pull requests. I wasn't aware that there was a

Bug#881719: libcdio 2.1.0 and lubcdio++

2020-05-24 Thread Vasyl Gello
Dear colleagues, Gabriel has prepared 2.1.0 in his Salsa repo and I added C++ interfaces needed by Kodi 19.0: https://salsa.debian.org/gabrielftg-guest/libcdio/-/merge_requests/1 Can the version 2.1.0 be pushed into distribution? --  Vasyl Gello signature.asc Description: PGP signature