Re: Notice of mailing list closure: pkg-multimedia-maintainers
On Wed, Apr 11, 2018 at 09:05:41AM +0100, James Cowgill wrote: > Given that the vast majority of packages are still on the old > lists.alioth.debian.org maintainer address, I think we will need the > list migrated otherwise the team will be screwed. Have I missed something? Mhh, yes indeed. James: do you have time to either get ahold of siretart by tomorrow, or get formorer appoint you as an ML admin, so you can then ask the alioth-lists team to migrate it? Otherwise I can deal with formorer and become myself an admin. But rather, also that new ML is something temporary that will go away in few years, so really, please people remember to switch to the @l.d.o ML… -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Accepted inkscape 0.92.3~pre0-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 05 Mar 2018 21:53:25 +0100 Source: inkscape Binary: inkscape Architecture: source Version: 0.92.3~pre0-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers <debian-multime...@lists.debian.org> Changed-By: Mattia Rizzolo <mat...@debian.org> Description: inkscape - vector-based drawing program Closes: 867083 Changes: inkscape (0.92.3~pre0-1) unstable; urgency=medium . [ Mattia Rizzolo ] * New upstream version 0.92.3~pre0. http://wiki.inkscape.org/wiki/index.php/Release_notes/0.92.3 + Compact layout for Document Properties. Closes: #867083; LP: #1510831 * d/control: Update Maintainer address to move away from alioth. * Rename d/mime to d/inkscape.mime for consistency. * Drop patch for poppler 0.58, applied upstream. . [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org Checksums-Sha1: 5c760c35c1cc9909fe3fa09b243feaf1aaa45130 2839 inkscape_0.92.3~pre0-1.dsc 2c0468b37de774afb0c43d883dbceba53f84fc12 31242832 inkscape_0.92.3~pre0.orig.tar.bz2 43c64f8d9c60f3b772534f28ac4b26ccad3065f9 181 inkscape_0.92.3~pre0.orig.tar.bz2.asc be06241f73b6ef5c47c84b28d1a6fabd9f86d895 27732 inkscape_0.92.3~pre0-1.debian.tar.xz 67fa0610b95a78b53fdb4171663d9e5d3984c03a 15481 inkscape_0.92.3~pre0-1_amd64.buildinfo Checksums-Sha256: 6350c99d7129c24a7f5f69ae1cc29639e9057c70e68b22cf98d48dbde21c82d8 2839 inkscape_0.92.3~pre0-1.dsc e41ee66069367fe7b55a4ca8dc245f9a071ae1173c2d4d3629db2e8a8db9c7d7 31242832 inkscape_0.92.3~pre0.orig.tar.bz2 6eb644d9e34ac15d6b1d3ea03c78ba20cc35d87070de8ab6ac07ad2c1b9c4532 181 inkscape_0.92.3~pre0.orig.tar.bz2.asc d6555388cda79ffc24a33f042b22a7d75c27f12088faf2c233127b31ca3303b9 27732 inkscape_0.92.3~pre0-1.debian.tar.xz 28bfeeb2ea1ca2e20c9edb03ccd07ade0cc35b8f86ccce78813f0241f30b2b5d 15481 inkscape_0.92.3~pre0-1_amd64.buildinfo Files: ac496178c4b2749c82e64398136096dc 2839 graphics optional inkscape_0.92.3~pre0-1.dsc 9cce565b955e6c9f0595d5b91ee246de 31242832 graphics optional inkscape_0.92.3~pre0.orig.tar.bz2 89ec23181547f7d3ffb0993cfaf2f692 181 graphics optional inkscape_0.92.3~pre0.orig.tar.bz2.asc 909234f9e5f0a3b491d1138c0f5185e0 27732 graphics optional inkscape_0.92.3~pre0-1.debian.tar.xz 6dae167a948b3d452b810cddada41e38 15481 graphics optional inkscape_0.92.3~pre0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlqdyFoACgkQCBa54Yx2 K60A4Q/9GXoDenxGcZYIEyF/tLfxRzAIikvLTq+8J+Cu1SG7QbQTa2FCTiUANkDb +ef+g4YYM5BXS959vBHUvGJ1yOsVv6BuEVNFoQTsQ3yMVXWNkLjEgnrK/ad1FaKv b5mKPJzQkWj5OnE2OPvSs2BgChKTXZQd6cxuvpIyU9NFMK0tOfxKrwKbe/4YK61Q xJ2yaL4Q/AYVjbJRFi7kqmtmUpufdk6RxPugwajvMEk/cOf96CHKJrkIRBn0yLAd d1FEV+y2Pj1v4eCxCOk24JGyQuDXC8atzyh22Rzd3P0Z8Oh6PQ2GhYRX74IsCQVO KsctoiOrppBA5R5KnUBUMpRtZqM49TZK2Y7pGS0qGTDLHQdx+9ZnWUPZmXKjyCtb I2q2FmmfCxbkUFe5xBgFX+X6pRJDbd6hRv+OYQ+h76qJBUKC/3SaMLolXIMLgL23 ncQhDUV70FBy3cGdKoUq8vpF9JjlKfuhkSjLA6zckXzkpEB2PrUdTS/g7+D1+u4D bCa5CKGDxzfb79zoVU/7o9f3HPQ/vxQQdtiIVBx62Zh/nQHQG1pAmExZZDK1nvqU jW1ySsmrN2I1HdCcLKOZbycx+8VnJdGlJGVB96cGxTqytebT1l9KoipmI/r1/x4s oX3J6rbMlm1XboX0aqRe8Dk0bMDDdJYluwTrANEywSaHUSTAMOc= =H7++ -END PGP SIGNATURE- ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Proposed multimedia team migration to salsa.d.o
On Mon, Feb 26, 2018 at 10:12:08AM +0100, IOhannes m zmölnig (Debian/GNU) wrote: > On 02/26/2018 09:50 AM, Mattia Rizzolo wrote: > > yes, please confirm them that they should leave it behind. > > > just so i understand it (being a non-native, i sometimes screw up with > phrases to mean the exact opposite): with "leave it behind" you mean > that they should abandon it so that in the mid future there will be no > more <pkg-multimedia-maintainers@lists.alioth.debian.org> list? I mean, let pkg-multimedia-maintainers@ die with alioth. > having said that, i'm all for abandoning the > pkg-multimedia-maintainers@lists.alioth.d.o list in favour of > debian-multimedia@l.d.o BTW: udd=> select count(distinct source) from sources where distribution = 'debian' and release = 'sid' and maintainer_email = 'debian-multime...@lists.debian.org'; count --- 87 (1 row) udd=> select count(distinct source) from sources where distribution = 'debian' and release = 'sid' and maintainer_email = 'pkg-multimedia-maintainers@lists.alioth.debian.org'; count --- 458 (1 row) I believe we've been forgetting to move the packages while uploading them recently… -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Proposed multimedia team migration to salsa.d.o
On Mon, Feb 26, 2018 at 12:22:35AM +, Reinhard Tartler wrote: > I just got an email as one of the "list owners" of > pkg-multimedia-maintainers@lists.alioth.debian.org - the basic question is > whether we want to continue using the list (on the new migration host) or > whether we abandon it in favor of debian-multime...@lists.debian.org > > In the past, we used both lists with different emphasis. From the > discussion of this thread, I believe the answer the latter, but I wanted to > check for other opinions and thoughts on this. yes, please confirm them that they should leave it behind. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Accepted jackd2 1.9.10+20150825git1ed50c92~dfsg-6 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 22 Feb 2018 11:51:02 +0100 Source: jackd2 Binary: jackd2 libjack-jackd2-0 jackd2-firewire libjack-jackd2-dev Architecture: source Version: 1.9.10+20150825git1ed50c92~dfsg-6 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers <pkg-multimedia-maintainers@lists.alioth.debian.org> Changed-By: Mattia Rizzolo <mat...@debian.org> Description: jackd2 - JACK Audio Connection Kit (server and example clients) jackd2-firewire - JACK Audio Connection Kit (FFADO and FreeBoB backends) libjack-jackd2-0 - JACK Audio Connection Kit (libraries) libjack-jackd2-dev - JACK Audio Connection Kit (development files) Closes: 853461 872831 Changes: jackd2 (1.9.10+20150825git1ed50c92~dfsg-6) unstable; urgency=medium . * Team upload. . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field. * d/control: Set Vcs-* to salsa.debian.org. . [ Mattia Rizzolo ] * Fix FTBFS with GCC 7. Closes: #853461 * Revert "libjackserver is a private library and does not need to be exported" It may even be a private library, but it's in a public namespace, so it needs to be dealt with as public. This reverts commit f1b2acff8fc96b2692206ecc2c0ac57043410569. Closes: #872831 Checksums-Sha1: e55cfe59731564632f9accb43994be1fb7b8a3e3 2650 jackd2_1.9.10+20150825git1ed50c92~dfsg-6.dsc 0daf9d9310c4a213194cc4c8cb1b0597923c5558 40368 jackd2_1.9.10+20150825git1ed50c92~dfsg-6.debian.tar.xz a1979003f49317dc2438c33dff4a4cf1041b4c56 9526 jackd2_1.9.10+20150825git1ed50c92~dfsg-6_amd64.buildinfo Checksums-Sha256: 47aef1c695f78c7e0e203e254fa7b6572e9ab9eed4614b9640b13a030b3b51b4 2650 jackd2_1.9.10+20150825git1ed50c92~dfsg-6.dsc 1dc579ce985a9e5cda9e980e4f80eb67586928336e8c8539b2d086cee0e31883 40368 jackd2_1.9.10+20150825git1ed50c92~dfsg-6.debian.tar.xz 6ec7a85bd353efffe57a8f364eeeb14d1b439c84d9125f35a1ea3d40906c9e62 9526 jackd2_1.9.10+20150825git1ed50c92~dfsg-6_amd64.buildinfo Files: afc902a23b9a39fba368cbaba6e22e87 2650 sound optional jackd2_1.9.10+20150825git1ed50c92~dfsg-6.dsc 32bad38f07a0ef615974ffbd13171df4 40368 sound optional jackd2_1.9.10+20150825git1ed50c92~dfsg-6.debian.tar.xz 67fa9202de9d5d28f7ec0d11ae4e 9526 sound optional jackd2_1.9.10+20150825git1ed50c92~dfsg-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlqOorAACgkQCBa54Yx2 K62glhAAsjUeGcAtP5nRUNiUug1rHxgMChCjlyAF0g3ChscRKSaqZOPksFe5QeM+ 1fSZApoON2upa8w12AV5LeI3xGsG99MrWm6V+C7MT/gqQ5ayujTGbelkXFaxH2Ns PKWCEsAhEXHuDqcQ0Jcr4QsKmd9fiVMbmTM8aDfHfv2/fWy8hi4CoxcTCwkk0MBj hl+ssVgvy0XbRIMoi5yEx5hILPC46DV9zLKTM0vHlY6vk8uSW5Unkwq7mwIlVvnM 4frvH/hl/+MWek0jAWwND5Z9pOeIDMBif/zGUa9EQJigrruKgsr1GYahQDXIGGaH kTSnG7CZdWyxFYi1COPcoGKXuSzSFrg3/MLK6jKfgQlj+YFmtIcu96urPdXlQz7L zdplbZG5Rffyb68m2gDMifLmBMWiBLMjZ/xcEDiDz7/hjk7MgkzbPfX/WuEWOZMb /3DcFUjD/uVdaaqKUv1lgK3JAb2mjblST6Ii3ZiR7BCl1aBCHHQoEnhXUlh55aOV vKpbukzMDOsjoMG3OBzYq/DL19mD7xigrCV3792y8x39JZelKSlUQpZCkXweOrxo C0wydzJdhjArjqcZMxiekqDZMdnfLk4+cvRloi6ud/Uw+OIwENvalNRtP2ruK/RY 4MYUQHp0N6VMfRI3xqnJE/7NQvEP51YcJFIUaZ+ogZiiQQuGGP8= =pwVZ -END PGP SIGNATURE- ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: salsa commits ML
On Fri, Feb 02, 2018 at 09:14:13PM +0100, Jaromír Mikeš wrote: > > Are you subscribed to the 'vcs' keywords? Check out your subscriptions > > default. > > It looks like this was the point ;) Now I got some commits messages ... > > Thank you Mattia ... I think we should also update our wiki pages Rather than the debian-multimedia pages, I believe $somebody should rather invest some not-small amount of time in some serious tracker.d.o user documentation. There is https://tracker.debian.org/docs/ but that's mostly targeted to distro-tracker devs and anyway it's also quite lacking in some areas, or not totally up to date. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: salsa commits ML
On Thu, Feb 01, 2018 at 07:29:11PM +0100, Jaromír Mikeš wrote: > 2018-01-31 12:16 GMT+01:00 James Cowgill <jcowg...@debian.org>: > > > Hi, > > > > On 31/01/18 11:02, Mattia Rizzolo wrote: > > > On Wed, Jan 31, 2018 at 09:32:09AM +, James Cowgill wrote: > > >> pkg-multimedia-commits is dead now that things have been migrated to > > salsa. > > >> > > >> For salsa you can: > > >> - Join #debian-multimedia - all commits are sent there. > > >> - Subscribe to a package on tracker.d.o and enable the "vcs" keyword. > > > - join the multimedia team on tracker: https://tracker.debian.org/ > > teams/debian-multimedia/ > > > > > > Then you won't need subscribe to single packages. > > > > I remember trying this before, but tracker won't let me join the team > > (or any teams at all it seems). So there was also a bug that prevented joining a team if you had multiple emails registered in tracker. That's now fixed! (this also means I couldn't test it myself up until now, although I was part of a couple of teams I created and it works there). > Hmm I have "join multimedia team" but I didn't received single commit > message yet :( > Also subscribe to all packages one by one is not what I like :( > I want to see all commits as I am learning from other's work. Are you subscribed to the 'vcs' keywords? Check out your subscriptions default. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: salsa commits ML
On Wed, Jan 31, 2018 at 09:32:09AM +, James Cowgill wrote: > pkg-multimedia-commits is dead now that things have been migrated to salsa. > > For salsa you can: > - Join #debian-multimedia - all commits are sent there. > - Subscribe to a package on tracker.d.o and enable the "vcs" keyword. - join the multimedia team on tracker: https://tracker.debian.org/teams/debian-multimedia/ Then you won't need subscribe to single packages. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: salsa git push problem
On Mon, Jan 29, 2018 at 11:14:26PM +0100, Jaromír Mikeš wrote: > $ git push https://salsa.debian.org/multimedia-team/lv2 master > --follow-tags > Username for 'https://salsa.debian.org': mira-guest > Password for 'https://mira-gu...@salsa.debian.org': > remote: You are not allowed to push code to this project. > fatal: unable to access 'https://salsa.debian.org/multimedia-team/lv2.git/': > The requested URL returned error: 403 > > any idea what might be wrong? Of course, you weren't part of the team… Members have not been migrated, so you need to request access. I've now added you, so you should be able to push. BTW, ssh is consider nicer than https :P -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#888739: dbg package for kodi
Control: tag -1 moreinfo On Mon, Jan 29, 2018 at 01:38:10PM +0100, Mathieu Malaterre wrote: > Sometimes people will need to gdb and attach to kodi to debug > something. I would be nice to provide a kodi-dbg package directly. > Rebuilding kodi is time consuming. Obviously, kodi relies on autodbgsym: https://wiki.debian.org/AutomaticDebugPackages And indeed they are available here: http://cdn-fastly.deb.debian.org/debian-debug/pool/main/k/kodi/ Does that cover what you need? -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Proposed multimedia team migration to salsa.d.o
On Sun, Jan 28, 2018 at 04:37:36PM +, James Cowgill wrote: > Now that salsa is stable, I am going to start migrating things over. I Thank you for doing the work! > One other change from the proposed plan is the addition of the > "tagpending" webhook described here: > https://wiki.debian.org/Salsa/Doc#Dealing_with_Debian_BTS_from_commit_messages Yes please. Thank you for adding that. (btw, you didn't push that change into the git repo of your script) > I am also taking this opportunity to trim the repositories on alioth. > The repositories below will be omitted from the initial import (but will > still all be made read only). Can you please *move* the repositories that have been moved, instead of just making them read-only? moving them to a MOVED_TO_SALSA directory should make the situation pretty clear. I'm assuming we are going to remove them at some point (if nothing because I'd like to help avoid forcing the alioth admins to keep a huge snapshot once the host goes down). Of course, I'm assuming you are also going to open a MR to add http redirects from anonscm to salsa. > # Incorrect Package Naming > My script requires repo name = source package name at the moment so > these will be omitted. The pd-* repositories are special because they > need to be put in a separate group. Should they intentionally not have > the correct name - ie should "pd-lua" become "pd/lua" or "pd/pd-lua"? Please, let's keep repo name = source package name. So the package 'pd-lua' should have a repo 'pd-lua', wherever group it is in. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Bug#886237: transition: libgig
Control: tag -1 moreinfo Control: forwarded -1 https://release.debian.org/transitions/html/auto-libgig.html On Wed, Jan 03, 2018 at 01:40:20PM +, James Cowgill wrote: > On 03/01/18 13:18, Mattia Rizzolo wrote: > > On Wed, Jan 03, 2018 at 12:55:40PM +0100, Jaromír Mikeš wrote: > >> Can I upload new upstream version of gigedit now to experimental? ... > >> I am not DD just having DM flag for qsampler > > > > Usually uploading to experimental comes *before* opening a transition > > bug. > > Please upload to experimental and ping this bug once it passed new (and > > the reverse-depends still builds fine). > > I think you have misunderstood. libgig is the library undergoing a > transition and is already in experimental. gigedit is a reverse > dependency of libgig which currently FTBFS but a fix is ready to be > uploaded. Oh, yes, I totally misunderstood indeed. Then sure, you don't need to ask -release permission to upload anything to experimental. And I deem to say you may as well either just upload it to unstable right away (and then release team will rebuild it once libgig is uploaded), or just upload it right after libgig is uploaded to unstable. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Bug#886237: transition: libgig
Control: tag -1 moreinfo On Wed, Jan 03, 2018 at 12:55:40PM +0100, Jaromír Mikeš wrote: > Can I upload new upstream version of gigedit now to experimental? ... > I am not DD just having DM flag for qsampler Usually uploading to experimental comes *before* opening a transition bug. Please upload to experimental and ping this bug once it passed new (and the reverse-depends still builds fine). PS. don't Use Cc while submitting bugs, use X-Debbugs-Cc instead. https://www.debian.org/Bugs/Reporting#xcc -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#885988: python-pyo: Please replace --no-ddebs with --no-automatic-dbgsym (for dh_strip in d/rules)
On Mon, Jan 01, 2018 at 11:40:15AM +0100, Niels Thykier wrote: > python-pyo is one of the two packages that uses the original option > "--no-ddebs". This was renamed to "--no-automatic-dbgsym" (among > other because Debian decided on not using ".ddeb" as extension). > > Please migrate to --no-automatic-dbgsym on your next upload. Better yet, please enable them. Why were they disabled? The changelog doesn't even mention this change, and the git log just says "disable dbgsym for now". -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#885108: inkscape: Consider dropping gnome-pkg-tools Build-Depends
On Sat, Dec 23, 2017 at 05:01:02PM -0500, Jeremy Bicha wrote: > inkscape was recently demoted to Ubuntu universe. (It appears to have > been kept in "main" a bit longer than necessary.) It's not like I diskliked having it in main, mind you! :) (wouldn't that imply that Canonical was supposed to provide support for it?) > Unless a package opts in or out, main packages participate in Ubuntu's > language packs and universe packages don't. I don't see a particular > reason to opt in here. I know nothing about l10n/i18n. Do somebody need to do anything special to get the translations out of the langpack? Also, what about anything that was done through https://translations.launchpad.net/ubuntu/+source/inkscape ? > Therefore, feel free to drop the gnome-pkg-tools Build-Depends added > in inkscape 0.91-11. There's no urgency although I think we should at > least do a rebuild of inkscape in Ubuntu before 18.04 LTS is released. Sure, I'll make sure it gets done before bionic releases. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: yoshimi_1.5.6-1_amd64.changes REJECTED
On Thu, Dec 21, 2017 at 08:48:16AM +0100, Jaromír Mikeš wrote: > Is that correct? Is the CC text that's there the 3.0 one? TBH, I'm nowhere in the mood of checking all of copyrights myself, but what's written in d/copyright now makes sense anyway. If you confirm the above I could try uploading again. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: yoshimi_1.5.6-1_amd64.changes REJECTED
[ dropping Chris and ftpmaster@ as requested ] On Wed, Dec 20, 2017 at 10:04:37PM +0100, Jaromír Mikeš wrote: > There is no hint on copyright holder in svg files How so, it looks pretty clear to me: https://sources.debian.org/src/yoshimi/1.5.5-2/Util/YoshimiSplash.svg/#L5-L9 |Cloud image used in the overlay created by | |Arun Kulshreshtha, 2006 | |accessed from: https://commons.wikimedia.org/wiki/File:Above_the_Clouds.jpg Seriously, are you even trying to look for it? > and there is this link: > https://creativecommons.org/ns > Maybe this was interpreted as CC-BY license by decopy? Right. And indeed I fail to parse that, but AFAIK that's a petty teplate of inkscape, and by itself that tag doesn't convey anything… But sometimes svg files has the correct metadata in the right tags; rarely, but happens :) However, there is a hint that to the original file used, which is taken from wikipedia and it is |Copyright: 2006 Arun Kulshreshtha |License: CC-BY-3.0 (the us variant) And it's clearly modified so it probably should also bear the copyright of somebody else, but to me it looks like nobody claimed it, so ignore this part… The other svg Util/splashreference.svg instead doesn't have anything, and it clearly is an original work of yoshimi's developers, so IMHO it falls under the "global" copyright/license paragraph. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: yoshimi_1.5.6-1_amd64.changes REJECTED
On Wed, Dec 20, 2017 at 06:17:10PM +0100, Jaromír Mikeš wrote: > I have used decopy app for first generating copyright file and than I edit > it manually. Let me recommend to always check what automated tools thinks of a copyright or license of a file. I have yet to meet with something that does a good enough work to actually save me time. > So for those two examles above there was no "Copyright" field at all but > linthian complained about it. Rightly so. > Should be these paragraphs removed removed as there is no copyright holder? No, they should be appropriately fixed to list the real copyright owner. Also, this question makes me wonder on whether you have any basic knowledge about intellectual property, but alas I don't really have any idea where to point you for more information. > Similar goes for license CC-BY it just has been without a version so I > hoped v3.0 is fitting. > Actually I am quite curious how decopy generate license from svg files. SVG is just a text file (an XML), just open it with your preferred text editor. Util/YoshimiSplash.svg even has a human-readable comment in it with the information you are looking for. The xiz files seems to be gzip-compressed XML as well, just opening a random one (with zless) I can see this: |(c) Dario Straulino |License: GPLv3 Guess the others are in a similar situation. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: yoshimi_1.5.6-1_amd64.changes REJECTED
On Wed, Dec 20, 2017 at 03:39:29PM +0100, Jaromír Mikeš wrote: > Ok ... I beleave it is fixed now in our git repo. > Mattia can you check it and upload again please? I haven't looked at the whole d/copyright, but just looking at a small commit: --- a/debian/copyright +++ b/debian/copyright @@ -103,9 +103,10 @@ Copyright: 2011, Alan Calvert 2014-2017, Will Godfrey License: GPL-3+ -Files: banks/Drums/0004-Natural Drum Kit.xiz - banks/Drums/0005-Natural Snare - variable deca.xiz - banks/Drums/0006-HiHat closed - variable decay.xiz +Files: banks/Drums/0004-Natural?Drum?Kit.xiz + banks/Drums/0005-Natural?Snare?-?variable?deca.xiz + banks/Drums/0006-HiHat?closed?-?variable?decay.xiz +Copyright: no-copyright License: GPL-3 Files: src/Misc/Config.cpp @@ -122,6 +123,7 @@ License: GPL-2+ or LGPL-2+ Files: Util/YoshimiSplash.svg Util/splashreference.svg +Copyright: no-copyright License: CC-BY That's not going to fly: * "no-copyright" is hardly a copyright holder (which afaik is "required" by both GPL-3 and CC-* * CC-BY: what version? you dumped a whole license text, so I guess you know what the answer * peaking further I see that you included the COPYING file as a copyrighted thing in the paragraph at line 99; whilst due to the initial Files:* it's included anyway, I don't think it should stay in a paragraph of its own, I'm pretty sure the GPL-2/3 text is not copyrighted by those two guys; besides, 'License: GPL-3+' for the GPL-2 text :P -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: yoshimi_1.5.6-1_source.changes REJECTED
On Sun, Dec 17, 2017 at 04:37:43PM +0100, Jaromír Mikeš wrote: > Hmmm ... ouh ... well ... can some DD upload this for me please? Uploaded :) (also, I pushed a commit to the repo) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: libmatroska_1.4.8-1.1_i386.changes ACCEPTED into unstable
On Tue, Oct 03, 2017 at 11:19:59AM +, Debian FTP Masters wrote: > Accepted: […] > Maintainer: Debian Multimedia Maintainers > <pkg-multimedia-maintainers@lists.alioth.debian.org> > Changed-By: Christian Marillat <maril...@debian.org> […] > Changes: > libmatroska (1.4.8-1.1) unstable; urgency=medium > . >* Non-maintainer upload. >* Upload to unstable to really closes #877497. Chrisitan, I find this upload of yours completely inappropriate and really offensive to the maintainer. This, and your message https://bugs.debian.org/877497#22 - as I wrote there Matteo had his reasons to upload to experimental first, and overriding him in what is a 0-hour, without any notice NMU this way is utterly insulting. I don't speak for Matteo (of course), but that's what I would feel if I were him. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#877497: closed by m...@debian.org (Matteo F. Vescovi) (Bug#877497: fixed in libmatroska 1.4.8-1)
On Tue, Oct 03, 2017 at 11:27:01AM +0200, Christian Marillat wrote: > > Changes: > > libmatroska (1.4.8-1) experimental; urgency=medium > > . > >* New upstream release (Closes: #877497) > > It's a joke ? > > This package is needed by mkvtoolnix in unstable not experimental. Uploading new versions of libraries to experimental is standard practice (even if not strictly required when there is no transition involved) to check for regressions and to things like test rebuilds. > Please upload new packages to unstable. Please change your tone, it feels very aggressive from this side, to a contributor that a bug you opened in less than 24 hours. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#871652: jnoise: Italian translation of package description has a little typo
Control: tag -1 l10n On Thu, Aug 10, 2017 at 02:24:41PM +0200, Leandro Noferini wrote: > Package: jnoise > Severity: minor > > The word "rumero" is a typo for "rumore" -> noise This is not coming from the package itself, but from the DDTP. CCing debian-i...@lists.debian.org as I have no idea how to update the translated description of the packages. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: [SCM] audacious/master: More updates to the symbols from the buildd logs
On Thu, Aug 24, 2017 at 10:06:25PM +0100, James Cowgill wrote: > Hi, Hi! > On 24/08/17 21:17, mat...@users.alioth.debian.org wrote: > > The following commit has been merged in the master branch: > > commit d746fd35d54cc052c950c09ac036c0bc3b7b25c8 > > Author: Mattia Rizzolo <mat...@debian.org> > > Date: Thu Aug 24 22:16:02 2017 +0200 > > > > More updates to the symbols from the buildd logs > [...]> @@ -18,7 +18,7 @@ libaudcore.so.5 libaudcore5 #MINVER# > > _Z11str_to_utf8PKci@Base 3.8 > > _Z11str_tolowerPKc@Base 3.8 > > _Z11str_toupperPKc@Base 3.9 > > - (arch=amd64)_Z11str_vprintfPKcP13__va_list_tag@Base 3.9 > > + (arch=amd64 s390x)_Z11str_vprintfPKcP13__va_list_tag@Base 3.8 > > (arch=i386 ppc64el)_Z11str_vprintfPKcPc@Base 3.9 > > (arch=arm64 armhf)_Z11str_vprintfPKcSt9__va_list@Base 3.9 > > I had a brief look at the GCC source and unfortunately there is no > pattern here. Every architecture represents va_list differently :( One way would be use pkgkde-symbolshelper's subst feature, but that requires adding it as a build-dep. > > _Z11strcmp_safePKcS0_i@Base 3.8 > > @@ -71,7 +71,8 @@ libaudcore.so.5 libaudcore5 #MINVER# > > _Z15filename_expandO9StringBuf@Base 3.8 > > _Z15filename_to_uriPKc@Base 3.8 > > _Z15hook_dissociatePKcPFvPvS1_ES1_@Base 3.8 > > - (subst)_Z15str_format_time{int64_t}@Base 3.8 > > + (arch=amd64 arm64 ppc64el s390x)_Z15str_format_timel@Base 3.9 > > + (arch=armhf i386)_Z15str_format_timex@Base 3.9 > > But in this case (and most others), you could use (arch-bits=XX) to save > you some work. Probably. I'm waiting for *all* the Debian buildds to finish before going ahead and updating them again (and do another upload). -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Fwd: Request to Join Project Debian Multimedia Maintainers from Simon Quigley (tsimonq2-guest)
On Thu, Aug 24, 2017 at 06:54:55PM +0200, Ross Gammon wrote: > On 08/24/2017 04:33 PM, Simon Quigley wrote: > >> Please read our packaging guidelines: > >> https://wiki.debian.org/DebianMultimedia/DevelopPackaging > >> If you need help with basic packaging skills, I recommend using Debian > >> Mentors (https://mentors.debian.net/intro-maintainers), although we have > >> some nice helpful people here in the team (time permitting). > > Thanks for the links! > > Looks like you don't need it and Mattia is on the case already :-) Yeah, we've worked together for a long time (well, several months anyway) :) Indeed I believe I have some faults in having it join :P Re: audacious: I went ahead and uploaded it, following Simon's pressure as he wanted to have a newer version in Ubuntu's 17.10. I don't quite understand why it stayed in git without anybody uploading it, but then again the person doing the updates in git never asked for sponsorship either… -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: qm-dsp DM flag
On Fri, Aug 18, 2017 at 02:24:54PM +0200, Jaromír Mikeš wrote: > 2017-08-15 20:26 GMT+02:00 Jaromír Mikeš <mira.mi...@gmail.com>: > > can someone grant me DM flag for qm-dsp package. > > > > > ping ;) > I need this flag to close this bug: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872249 I won't grant you DM for the pacakge (you really need IOhannes for that), but I took the liberty of sponsoring the update. A couple of remarks: * the latest standards-version is 4.0.1. If you didn't know that please subscribe to debian-devel-announce and follow it * using 'debhelper (>= 10~)' is pointless: stable has > 10 already, and oldstable-bpo does as well: there is no suite with version "10" to backport from * the short description of libqm-dsp-dev says "headers" but it also contains the architecture-dependant symlink for the development library; personally I'd drop that word. * I find that gbp's postclone thing very weird: there is pretty much no way a random guy that clones and plans to upload the package runs it. Also, I have follow-tags in my ~/.gitconfig, and I deem to be able to deal with the .pc directory (btw, I usually add it to the main .gitignore file in my own packages) - just a comment on the weirdness in my opinion :) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Version 0.35.2-2 of guitarix is marked for autoremoval from testing on 2017-07-30.
On Thu, Aug 03, 2017 at 09:33:00PM +0200, Ross Gammon wrote: > On 03/08/17 20:54, Hermann Meyer wrote: > > Really, no one? > > > > It's a pity to see guitarix in debian in such a bad shape. I've tried to > > contact Víctor Cuadrado Juan, who is the current maintainer from the > > (Debian Multimedia Maintainers > > <https://qa.debian.org/developer.php?login=pkg-multimedia-maintainers@lists.alioth.debian.org>) > > team, for guitarix in debian, but get no response. > > > Please be a little patient. Victor maybe on holiday, travelling with > work, ill, or have a broken computer. The bug was only reported just > over a month ago, and that is not so long. Indeed, for Debian waiting one month is really little, despite that being an RC bug (besides, I'd have expected a severity:important bug and then be rised at a later date when removal of webkitgtk's removal loomed)… > > For me , as upstream maintainer, the current situation is a real pity. > > Guitarix is in debian since 2013 05 05 and I'm, as upstream maintainer > > have all the time full-fill any request of debian maintainers. > > Next removal is date is 2017-08-13. > > Seeing that it is for a "bug" witch is currently unrelated for > > debian-testing, is a way more annoying. > > > > Guitarix is not being removed from Debian, only from unstable, which is > not what most users are running. Correction: it's being removed from debian *testing*, as Hermann said, but indeed it's not so terrible: it will be back as soon as the bug is fixed. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#866532: inkscape: error while loading shared libraries: libgsl.so.19: cannot open shared object file: No such file or directory
On Wed, Jul 26, 2017 at 04:51:06PM +0200, José Luis García Pallero wrote: > inkscape: error while loading shared libraries: libgsl.so.19: cannot > open shared object file: No such file or directory > > I can't understand why inkscape is asking for libgsl.so.19 Indeed, please check again your inkscape installation. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#868612: mixxx: diff for NMU version 2.0.0~dfsg-7.1
On Mon, Jul 24, 2017 at 12:51:55PM +0100, Simon McVittie wrote: > I've prepared an NMU for mixxx (versioned as 2.0.0~dfsg-7.1) > incorporating the patch from James Cowgill for #868612 and the pending > change from pkg-multimedia git, and uploaded it to DELAYED/2. Please > feel free to tell me if I should delay it longer. > > The changes can also be fetched from the 'nmu' branch in this git > repository: https://anonscm.debian.org/git/users/smcv/mixxx.git I've merged your changes and added a tag to the git repository; please feel free to reschedule it to delayed/0. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#868841: [gwc] error processing archive /var/cache/apt/archives/gwc_0.22-1_amd64.deb
Control: severity -1 serious On Wed, 19 Jul 2017, 9:00 a.m. ,wrote: > Package: gwc > Version: 0.22-1 > Severity: normal > > --- Please enter the report below this line. --- > > # LANG=C apt full-upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages will be upgraded: > gwc > 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > Need to get 0 B/193 kB of archives. > After this operation, 52.2 kB of additional disk space will be used. > Do you want to continue? [Y/n] > Retrieving bug reports... 0% > Retrieving bug reports... Done > Parsing Found/Fixed information... Done > Lese Changelogs... Fertig > (Reading database ... 354627 files and directories currently installed.) > Preparing to unpack .../archives/gwc_0.22-1_amd64.deb ... > Unpacking gwc (0.22-1) over (0.21.19~dfsg0-7) ... > dpkg: error processing > archive /var/cache/apt/archives/gwc_0.22-1_amd64.deb (--unpack): trying > to overwrite '/usr/share/icons/hicolor/icon-theme.cache', which is also > in package medit 1.2.0-2+b2 Errors were encountered while > processing: /var/cache/apt/archives/gwc_0.22-1_amd64.deb E: > Sub-process /usr/bin/dpkg returned an error code (1) > Failure to install is RC. > ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#867083: Document Properties window/dialog is out of screen bounds
Control: tag -1 upstream confirmed Control: forwarded -1 https://bugs.launchpad.net/inkscape/+bug/1510831 On Mon, Jul 03, 2017 at 08:42:13PM +0100, Phil Wyett wrote: > Document Properties window/dialog is out of screen bounds at screen > resolution 1366x768. > > Activate: File -> Document Properties > > See attached screenshot. Yes, known upstream bug, see link above. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#864415: [inkscape] crash while rotating with snap to path
Control: forwarded -1 https://bugs.launchpad.net/inkscape/+bug/1701930 Control: tag -1 upstream Control: severity -1 normal Sorry, it slipped past me… On Fri, Jun 09, 2017 at 07:45:16PM +0200, Carsten Knoll wrote: > See the attached file. It crashes in 100% of cases, if I rotate the > dashed line as shown in the video. However there seem to be two > different types: Thanks for the reproducer, forwarded upstream in a new bug (linked above). The other bugs I could find seemed similar but different variation of this, I'll let upstream decide whether they are different or the same and in such case merge them. > a) slow rotation -> snap is indicated, then inkscape crashes but at > least creates a backup (that saved me a lot of time the other day!) Couldn't reproduce this, tbh. For how slow I could rotate it it always crashed hard as in case b. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#866532: inkscape: Fails to start because of libgsl.so.0 can't be found
Control: tag -1 moreinfo unreproducible On Fri, Jun 30, 2017 at 12:33:44AM +0200, greggy wrote: > Inkscape fails to start with the following error message: > > $ inkscape > inkscape: error while loading shared libraries: libgsl.so.0: cannot open > shared object file: No such file or directory > > The problem appeared after I upgraded my system from jessie to stretch. Of course I can't reproduce it… I given how widespread inkscape is and you're the only one reporting it makes me believe there is something wrong on your side. For example, are you sure you are running the binary coming from the Debian archive? Our inkscape should be built against libgsl.so.19, not libgsl.so.0 as your error message reports. It makes me believe you somehow have the binary coming from jessie, which was built against libgsl.so.0 indeed. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#864415: [inkscape] crash while rotating with snap to path
Hi Carsten, On Thu, Jun 08, 2017 at 11:39:28AM +0200, Carsten Knoll wrote: > Reproducible crash when rotating a line whish should snap to another > line (path). See video: > > https://vimeo.com//220771887 Wow, nice crash… > About Dialog says w.r.t. version: Inkscape 0.92.1 r15371 > If it helps i can provide the file where this occurs I've talked to upstream, and they are aware of several crashes related to snapping (which means you should be able to workaround it disapling the snap). If possible I'd like to have that fail, so I can reproduce the crash and check which one of the upstream report it is, so to link the bug (I want to get a traceback, but also would like to send that file upstream, as several of the crashing files are really complex compared to yours). Thank you for the report! -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#853453: Fwd: [Inkscape-devel] Stable 0.92.1 and gcc-7
0) - static_cast(amop ? unpremul_alpha(bmop, amop) : 0)); +return ((diff / 3) <= ((threshold * 3) / 4)); +} case FLOOD_CHANNELS_H: return ((int)(fabs(hsl_check[0] - hsl_orig[0]) * 100.0) <= threshold); case FLOOD_CHANNELS_S: -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Inkscape-devel mailing list inkscape-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel - End forwarded message - -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#859280: Updating the rem Uploaders list
Source: rem Version: 0.5.0-3 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Ramakrishnan Muthukrishnan <rkrish...@debian.org> has retired, so can't work on the rem package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#858525: libjack-jackd2-dev: Depend on jackd2
On Mon, Mar 27, 2017 at 11:22:41PM -0400, Reinhard Tartler wrote: > I think the approach of adding a 'depends' to jackd2 is the simplest. > Moving the shared library to the -dev packages doesn't work, because > /usr/bin/jackd2 and netserver.so link against it. Why not moving the file to libjack-jackd2-0 instead? > The downside of this patch is that every package that depends on > libjack-jackd2-dev now also pulls jackd2. This might be a bit overkill > (and potentially starts a daemon). To resolve this, I think we would > need to introduce a new package (which I'd rather avoid at this point). There is a slowly running thread in debian-devel right now exactly about library packages depending on programs (ok, here we are talking about the -dev package, not the library, but it fall close). -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#857582: inkscape: Inkscape gets stuck when you try to ungroup a complicated artwork
(please don't drop the bug from the recipients when talking about the bug and things that should be public) On Sun, Mar 12, 2017 at 06:32:09PM -0400, Daniele Antonucci wrote: > My Inkscape gets stuck and nothing more... > > Look at this: > > 10791 "USER" 20 0 1150888 556100 56100 R 100.0 3.4 34:16.71 > inkscape > > I am waiting for 34 minutes just because I launched the command simplify > the paths, right now the only I can do is setup at the best this artwork > and exporting it as png, hoping to do not get stuck also for this task. After some chat with upstream I can come to you with 2 known bugs: 1. inkscape was never that great when dealing with a huge amount of objects. Your document has 15625 objects. Ref: https://bugs.launchpad.net/inkscape/+bug/410240 2. if you have some particular dock opened (now, or in the past in the same session, i.e. closing them doesn't help), the performance is pretty bad; I could reproduce having inkscape stuck for more than 10 minutes before I killed it. Apparently this happens with things like the Objects dialog and the XML editor. Refs: https://bugs.launchpad.net/inkscape/+bug/1011726 https://bugs.launchpad.net/inkscape/+bug/1431274 Do you recognize yourself in one of those situation? Please try to run with a clean profile by: 1. closing all the running instances of inkscape 2. moving ~/.config/inkscape/preferences.xml away (you can reinstate it later) 3. import the .eps and try to ungroup it I'd expect it to take at most one minute. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#857267: inkscape: Clicking on export PNG does nothing.
Control: tag -1 moreinfo On Thu, Mar 09, 2017 at 12:52:48PM +0200, Mladen Mijatov wrote: > opening any SVG image and then going to "File -> Export PNG image" does > nothing. Pressing keyboard shortcut renders same behavior. > > Expected outcome is for export dialog to appear after which we can select the > location where exported image is to be stored. There is no dialog window that should appear. A dialog box appears in the dialog "dock", on the right of the screen. You may have hidden the dock, check by pressing F12 (or View → Show/Hide dialogs). Also see https://bugs.launchpad.net/inkscape/+bug/1270295 Do you confirm? -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#855904: "Trace Pixel Art" has no effect
Control: tag -1 moreinfo On Thu, Feb 23, 2017 at 09:43:18AM +0100, Vincent Bernat wrote: > Hey! Hi! :) > The "Path" → "Trace Pixel Art…" menu has no effect. No dialog, nothing > on stderr. If you see nothing is probably because you have hidden the dialogs, and in some cases opening a new one doesn't open the panel. There is a long standing bug with the GTK2 build: https://bugs.launchpad.net/inkscape/+bug/1270295 Does this match what you're seeing? > Inkscape tutorial says this feature uses libdepixelize > which doesn't seem to exist in Debian: Yes, but inkscape is bundling the library, and it statically links it (if you peak at the build log). -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#853453: inkscape: ftbfs with GCC-7
Control: severity -1 important (I want it higher in the otherwise too big bug list…) On Tue, Jan 31, 2017 at 09:32:15AM +, Matthias Klose wrote: > The package fails to build in a test rebuild on at least amd64 with > gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The > severity of this report may be raised before the buster release. > There is no need to fix this issue in time for the stretch release. > > The full build log can be found at: > http://people.debian.org/~doko/logs/gcc7-20170126/inkscape_0.92.0-4_unstable_gcc7.log > The last lines of the build log are at the end of this report. .. > Common build failures are new warnings resulting in build failures with > -Werror turned on, or new/dropped symbols in Debian symbols files. > For other C/C++ related build failures see the porting guide at > http://gcc.gnu.org/gcc-7/porting_to.html The actual error (I believe): |/<>/src/ui/tools/flood-tool.cpp:253:119: error: call of overloaded 'abs(unsigned int)' is ambiguous | diff += abs(static_cast(amc ? unpremul_alpha(bmc, amc) : 0) - (amop ? unpremul_alpha(bmop, amop) : 0)); | ^ |In file included from /usr/include/c++/7/cstdlib:75:0, | from /usr/include/c++/7/stdlib.h:36, | from /<>/src/trace/trace.h:17, | from /<>/src/trace/potrace/inkscape-potrace.h:20, | from /<>/src/ui/tools/flood-tool.cpp:24: |/usr/include/stdlib.h:735:12: note: candidate: int abs(int) | extern int abs (int __x) __THROW __attribute__ ((__const__)) __wur; |^~~ |In file included from /usr/include/c++/7/cstdlib:77:0, | from /usr/include/c++/7/stdlib.h:36, | from /<>/src/trace/trace.h:17, | from /<>/src/trace/potrace/inkscape-potrace.h:20, | from /<>/src/ui/tools/flood-tool.cpp:24: |/usr/include/c++/7/bits/std_abs.h:56:3: note: candidate: long int std::abs(long int) | abs(long __i) { return __builtin_labs(__i); } | ^~~ |/usr/include/c++/7/bits/std_abs.h:61:3: note: candidate: long long int std::abs(long long int) | abs(long long __x) { return __builtin_llabs (__x); } | ^~~ |/usr/include/c++/7/bits/std_abs.h:70:3: note: candidate: constexpr double std::abs(double) | abs(double __x) | ^~~ |/usr/include/c++/7/bits/std_abs.h:74:3: note: candidate: constexpr float std::abs(float) | abs(float __x) | ^~~ |/usr/include/c++/7/bits/std_abs.h:78:3: note: candidate: constexpr long double std::abs(long double) | abs(long double __x) | ^~~ |/usr/include/c++/7/bits/std_abs.h:84:3: note: candidate: constexpr __int128 std::abs(__int128) | abs(__GLIBCXX_TYPE_INT_N_0 __x) { return __x >= 0 ? __x : -__x; } | ^~~ |/usr/include/c++/7/bits/std_abs.h:102:3: note: candidate: constexpr __float128 std::abs(__float128) | abs(__float128 __x) | ^~~ There are other instances of the same error in previous lines in the same file. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#852290: inkscape: saving as "optimised SVG" fails, due to error when importing scourString
Control: notfound -1 0.92.0-3~bpo8+1 Control: found -1 0.92.0-2 Control: retitle -1 inkscape: fails with older python-scour (as found in jessie) On Mon, Jan 23, 2017 at 11:19:46AM +0100, Tim Wienk wrote: > Package: inkscape > Version: 0.92.0-3~bpo8+1 > > Please note, this bug only applies to Debian Jessie (using inkscape from > jessie-backports and python-scour from jessie - there is no backported > version of python-scour). Thanks for the bug report! Unfortunately the Debian bug tracker doesn't really know about backports, but anyway, this is (should, haven't yet tried myself) actually a bug reproducible in the unstable version of inkscape with just a older version of python-scour. Note that it can't be workarounded in the packaging side by backporting the newer python-scour and forcing an higher version, as python-scour is only "Recommend"ed, and versioned recomends are not really considered. > When saving as an optimised SVG, inkscape uses the scour library to > optimise the SVG. An error is reported when doing so, triggered by > importing `scourString` from `scour.scour`. > > The problem is most likely a result of a change in the python-scour > package: > > - In package version 0.26-3 (jessie), scour.py exists as: > /usr/lib/python2.7/dist-packages/scour.py > - In package version 0.32-2 (stretch), scour.py exists as: > /usr/lib/python2.7/dist-packages/scour/scour.py Thank you for the analysis! > I have implemented the following patch locally to work around the > problem: > > --- /usr/share/inkscape/extensions/scour.inkscape.py~ > +++ /usr/share/inkscape/extensions/scour.inkscape.py > @@ -6,3 +6,6 @@ > import scour > -from scour.scour import scourString > +try: > +from scour.scour import scourString > +except Exception as e: If anything, this should catch inly ImportError over all of Exception (besides, there is no need to keep the exception info in the 'e' variable here). > +from scour import scourString > except Exception as e: I'll forward this upstream soon. Thank you again for your bug! -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#816494: inkscape: crash when reading PDF with 'import via Poppler' ticked
Control: tags -1 - moreinfo unreproducible + confirmed upstream pending On Tue, Jan 03, 2017 at 03:18:22PM +, Edward Betts wrote: > Mattia Rizzolo <mat...@debian.org> wrote: > > I can't reproduce this at all with 0.92; could you please try with the > > .deb I uploaded to > > https://volatile.mapreri.org/2017-01-03/8322a737d1f856934c62883734bd27b1/inkscape_0.92~pre4-0~exp0_amd64.deb > > No crash with 0.92 Thanks for checking. I'm not sure which particular change since 0.91 fixed this (a lot changed, as you guess..), and I don't think it'd be good use of my time to track it down; I'll close this bug with new upstream (that, btw, I don't think will hit stretch, it's too late for that). Thank you again for reporting this bug! -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#816494: inkscape: crash when reading PDF with 'import via Poppler' ticked
On Tue, Jan 03, 2017 at 01:56:14PM +, Edward Betts wrote: > I tested again, same problem. I'm using 0.91-12+b1 > > Did you tick the 'import via Poppler' box? Yes I did. Now I tried again and I noticed that I can reproduce this only if I start inkscape by inkscape additional-card-request.pdf in a terminal (or probably also if I load the pdf directly at inkscape startup); instead if I open inkscape with a blank document, and then do File → Import, it doesn't crash; odd. I can't reproduce this at all with 0.92; could you please try with the .deb I uploaded to https://volatile.mapreri.org/2017-01-03/8322a737d1f856934c62883734bd27b1/inkscape_0.92~pre4-0~exp0_amd64.deb (sha256: d1da977e44c3fc81262f30fa9042dec12e494d5fcd8e90e8bfab931705f831aa) Thank you in advance. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#822579: inkscape: may mess up with hatches, when importing DXF files
Control: tags -1 upstream Control: forwarded -1 https://bugs.launchpad.net/inkscape/+bug/1653707 On Mon, Apr 25, 2016 at 04:18:24PM +0200, Francesco Poli (wintermute) wrote: > Hello and thanks for maintaining Inkscape in Debian! Hi Francesco! > Please investigate and/or forward my bug report upstream, as appropriate. I can still reproduce this with the dev version 0.92~pre4, so I forwarded it upstream. Thank you for reporting this bug! -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#816494: inkscape: crash when reading PDF with 'import via Poppler' ticked
control: tag -1 moreinfo unreproducible Hi Edward, thank you for your bug report. On Wed, Mar 02, 2016 at 10:53:32AM +, Edward Betts wrote: > Loading a PDF, if I tick the 'import via Poppler' box then inkscape crashes. > > I rebuilt inkscape with debugging symbols and was able to reproduce the crash. > > The PDF that caused the crash is available here: > > > http://static.halifax.co.uk/assets/pdf/creditcards/pdf/additional-card-request.pdf I just tried it with inkscape 0.91-12+b1, and I couldn't reproduce it (as I can't with the dev version 0.92~pre4 that I have locally). Benda said he could reproduce with 0.91-11. > Here is the backtrace from gdb: > > Core was generated by `inkscape additional_card_request.pdf'. > Program terminated with signal SIGSEGV, Segmentation fault. > #0 0x7f6c18f69075 in has_case_prefix (haystack=haystack@entry=0x0, > needle=needle@entry=0x7f6c18fd13c4 "file:/") at > /build/glib2.0-2.46.2/./glib/gconvert.c:1267 > 1267/build/glib2.0-2.46.2/./glib/gconvert.c: No such file or directory. > [Current thread is 1 (Thread 0x7f6c21524ac0 (LWP 12292))] > (gdb) bt > #0 0x7f6c18f69075 in has_case_prefix (haystack=haystack@entry=0x0, > needle=needle@entry=0x7f6c18fd13c4 "file:/") at > /build/glib2.0-2.46.2/./glib/gconvert.c:1267 > #1 0x7f6c18f6a4a2 in g_filename_from_uri (uri=uri@entry=0x0, > hostname=hostname@entry=0x0, error=error@entry=0x7ffe93a11240) at > /build/glib2.0-2.46.2/./glib/gconvert.c:1563 Also, this make me think the crash actually happened somewhere in glib2.0, rather than inkscape itself. Could you please try it again? -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#810792: inkscape: systemd-plot.svg can't be read (one example attached)
control: severity -1 normal control: forwarded -1 https://bugs.launchpad.net/inkscape/+bug/1653694 control: tag -1 upstream On Tue, Jan 12, 2016 at 11:01:42AM +0100, Thomas Schmidt wrote: >* What led up to the situation? > > Trying to read a so called *.svg, the file attached is a shame (*XML-crap!) well, it's a regular xml file, nothing particularly shameful or crappy about it. Also, the file is not attached, but reported inline, which required additional work to extract it; please next time actually *attach* the file. Furthermore it'd be useful to know the origin of the file. There is a comment in it saying it's coming from systemd-analyze, I trust the comment to be correct. >* What was the outcome of this action? > > Nothing That's not a useful answer to that question. If I try to open it inkscape shows me a white page instead of the actual graph like chromium does. Forwarded upstream, see the link on the top of this message. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: [RFS] updated libva and intel-vaapi-driver bpos
On Mon, Nov 21, 2016 at 10:36:13PM -0500, Nicholas D Steeves wrote: > > > The libva version I've requested migrates to testing tomorrow, > > > assuming no bugs are reported in the next however many of hours :-) > > > > yeah, I'll wait for that to happen before looking at these anyway :P > > I want everything but backports-master chasing after me, that wouldn't > > be nice (also because I saw how bad that could be...). > > Sounds good! And uploaded both :) I've actually first uploaded libva this morning, and now, after 2 dinstalls, the built packages reached my mirror and I could build intel-vaapi-driver using them ;) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: [RFS] updated libva and intel-vaapi-driver bpos
On Mon, Nov 21, 2016 at 07:31:10PM -0500, Nicholas D Steeves wrote: > I have pushed updates. ack! > Proof that they build is here: > https://mentors.debian.net/package/libva > https://mentors.debian.net/package/intel-vaapi-driver bah, no need for mentors (for me at least); I'm very happy to just use the git repository. > I'm not sure what version of libva mentors builds intel-vaapi-driver > against, but it seems to have worked. ? mentors.d.n doesn't build anything. What do you mean by that? > When I built them locally I > built libva first, and copied the debs to my local repo. The clean > jessie pbuilder I use to build these intel-vaapi-driver then pulls in > whatever version it needs. Yeah, well, the build-dep is very clear on the need of 1.7.3 of libva :) In this case I usually test build locally by using the local repo, but then upload source only and the have the buildd figure what to do (they will not try the build until the needed libva is available). > Do you think the mipsel delays from the last run can be used to > predict $DELAY for an upload of intel-vaapi-driver to deferred/$DELAY? umh, not sure what you mean here? Why would we need to do anything to wait for mipsel? > The libva version I've requested migrates to testing tomorrow, > assuming no bugs are reported in the next however many of hours :-) yeah, I'll wait for that to happen before looking at these anyway :P I want everything but backports-master chasing after me, that wouldn't be nice (also because I saw how bad that could be...). -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: [SCM] hydrogen/master: Exclude .gitignore file from upstream tarball.
On Thu, Nov 10, 2016 at 06:52:14PM +0100, Jaromír Mikeš wrote: > >> +Files-Excluded: > >> + .gitignore > > > > You can't seriously be repacking the tarball just for this !? > > Hmm ... What do you suggest? > Just exclude gitignore file without adding repack suffix to upstream tarball? I suggest you don't repackage. Rather have upstream not include that file in their tarball, if anything. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#841853: inkscape: Mouse cursor is a white outline on PowerPC
Control: tag -1 pending On Mon, Nov 07, 2016 at 12:46:25PM -0500, Steven Gawroriski wrote: > > I'll see about uploading an updated debian package with this too. > > That would be cool. Committed: https://anonscm.debian.org/git/pkg-multimedia/inkscape.git/commit/?id=0be84125610e178c2e68fbc03f13ed88128a9d32 I'd like to also include anohter thing before uploading, but it'll come. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#838486: inkscape: Segmentation fault in 0-48.5 src/display/nr-arena-image.cpp
control: tag -1 upstream - patch On Wed, Sep 21, 2016 at 09:26:10PM +0200, Alessandro Vesely wrote: > I'll try and reapply the latter patch tomorrow, and see how it goes. How did that go? Also, would you mind checking this upstream with 0.92 and possibly forward port your patch to that too (and send the bug/MR upstream)? I plan to put the pre-releases of 0.92 in experimental at one point if you want prefer to wait for that (i.e. if you don't play nice with bzr). -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#841853: inkscape: Mouse cursor is a white outline on PowerPC
control: tag -1 fixed-upstream control: severity -1 minor On Sun, Nov 06, 2016 at 01:53:35PM -0500, Steven Gawroriski wrote: > Since today my internet connection is unusually and abysmally slow, > checking out of the Inkscape repository was essentially moving at > dial-up speeds. ouch, that must be awful! > So instead I have submitted a bug report with the attached patch, along > with a reference to this bug. > > * https://bugs.launchpad.net/inkscape/+bug/1639611 Great! I also noticed that they committed the patch already in both trunk and 0.92.x (that, who knows, they might even release some day) I'll see about uploading an updated debian package with this too. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#841853: inkscape: Mouse cursor is a white outline on PowerPC
control: tag -1 upstream patch On Sat, Nov 05, 2016 at 07:06:04PM -0400, Steven Gawroriski wrote: > Taking a look at this myself. Thanks for doing it. > I wrote the attached patch which essentially byte swaps the value > before this function returns. The cursors are drawn correctly and > Inkscape can now be used much more easily. Thanks for the patch! > If a contributor agreement > is required then I would accept giving away my copyright for the code > contained in this patch. No CLA or stuff is needed, no. Though, I'd like to ask you to foward this patch upstream. It's enough to open a MR against https://code.launchpad.net/~inkscape.dev/inkscape/trunk for it. Could you do it? > Description: Swap before return sp_cursor_pixbuf_from_xpm on big endian. > This byte swaps before the return in sp_cursor_pixbuf_from_xpm on big > endian systems so that the cursor is made visible on these systems. > Author: Steven Gawroriski <ste...@multiphasicapps.net> > > --- > > Origin: other > Bug-Debian: https://bugs.debian.org/841853 > > --- inkscape-0.91.orig/src/sp-cursor.cpp > +++ inkscape-0.91/src/sp-cursor.cpp > @@ -106,6 +106,14 @@ GdkPixbuf *sp_cursor_pixbuf_from_xpm(gch > pixmap_buffer[y * width + x] = (it == colorMap.end()) ? 0u : > it->second; > } > } > + ↑↑↑ be aware of these 4 trailing whitespaces, some people don't like them. > +#if G_BYTE_ORDER == G_BIG_ENDIAN > +for (int i = 0, n = width * height; i < n; i++) > +{ > +guint32 v = pixmap_buffer[i]; > +pixmap_buffer[i] = ((v & 0xFF) << 24) | (((v >> 8) & 0xFF) << 16) | > (((v >> 16) & 0xFF) << 8) | ((v >> 24) & 0xFF); > +} > +#endif > > return > gdk_pixbuf_new_from_data(reinterpret_cast<guchar*>(pixmap_buffer), > GDK_COLORSPACE_RGB, TRUE, 8, width, height, width * sizeof(guint32), > free_cursor_data, NULL); > } -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: paulstretch dbg symbols missing
On Mon, Oct 31, 2016 at 05:38:31AM +0100, Jaromír Mikeš wrote: > 2016-10-30 22:27 GMT+01:00 Mattia Rizzolo <mat...@debian.org>: > > While on it let me suggest an edit: drop this from d/rules: > > > > override_dh_auto_install: > > mkdir -p $(DESTDIR)/usr/bin/ > > cp -a paulstretch $(DESTDIR)/usr/bin/ > > > > and instead use the d/paulstretch.install that you already have. > > Hi Mattia, > > thank you for help ... but unfortunately this doesn't make the magic > Build flags still not respected :( This suggestion of mine is totally orthogonal to the issue at hand. Can you share the current state of d/rules? -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: paulstretch dbg symbols missing
On Sun, Oct 30, 2016 at 09:25:45PM +, Mattia Rizzolo wrote: > On Sun, Oct 30, 2016 at 10:00:24PM +0100, Jaromír Mikeš wrote: > > while building paulstretch package dbgsym package doesn't contain > > debugging symbols. > > > > W: paulstretch-dbgsym: debug-file-with-no-debug-symbols > > usr/lib/debug/.build-id/6d/7f1e5e9e47ab9925bdea21e6907b6afb19.debug > > > > Any help please? > > That's because your package is not respecting dpg-buildflags(1) (also as > warned by bls[1]. > > You need to build with -g to get debug symbol and your package is not > building with that flag; also please don't inject that flag only, but > have your package respect all of the common build flags as exported by > dpkg, and only if needed tweak them by acting on the > DEB_BUILD_MAINT_OPTION variable as documented in dpkg-buildflags(1). > > [1] https://qa.debian.org/bls/packages/p/paulstretch.html While on it let me suggest an edit: drop this from d/rules: override_dh_auto_install: mkdir -p $(DESTDIR)/usr/bin/ cp -a paulstretch $(DESTDIR)/usr/bin/ and instead use the d/paulstretch.install that you already have. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: paulstretch dbg symbols missing
On Sun, Oct 30, 2016 at 10:00:24PM +0100, Jaromír Mikeš wrote: > while building paulstretch package dbgsym package doesn't contain > debugging symbols. > > W: paulstretch-dbgsym: debug-file-with-no-debug-symbols > usr/lib/debug/.build-id/6d/7f1e5e9e47ab9925bdea21e6907b6afb19.debug > > Any help please? That's because your package is not respecting dpg-buildflags(1) (also as warned by bls[1]. You need to build with -g to get debug symbol and your package is not building with that flag; also please don't inject that flag only, but have your package respect all of the common build flags as exported by dpkg, and only if needed tweak them by acting on the DEB_BUILD_MAINT_OPTION variable as documented in dpkg-buildflags(1). [1] https://qa.debian.org/bls/packages/p/paulstretch.html -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#838486: inkscape: Segmentation fault in 0-48.5 src/display/nr-arena-image.cpp
Hi Alessandro, On Wed, Sep 21, 2016 at 02:13:24PM +0200, Alessandro Vesely wrote: > $ gdb -q --args /usr/bin/inkscape test-pdf.svg > Reading symbols from /usr/bin/inkscape...done. > (gdb) run > Starting program: /usr/bin/inkscape test-pdf.svg > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > [New Thread 0x7fffe66dd700 (LWP 14025)] > [New Thread 0x7fff5442f700 (LWP 14030)] > [New Thread 0x7fff53bce700 (LWP 14033)] > > Program received signal SIGSEGV, Segmentation fault. > nr_arena_image_pick (item=0x29f5e00, p=..., delta=) at display > /nr-arena-image.cpp:318 > 318 return (pix_ptr[3] > 0) ? item : NULL; nasty crash. Now, that's the stable release, though. And most of the development efforts are concentrated in unstable. Can you please check whether the crash happens with 0.91? you can just use what you find in jessie-backports for that. > --- a/src/display/nr-arena-image.cpp > +++ b/src/display/nr-arena-image.cpp > @@ -303,17 +303,17 @@ > } else { > > unsigned char *const pixels = image->px; > -int const width = image->pxw; > -int const height = image->pxh; > -int const rowstride = image->pxrs; > +unsigned int const width = (unsigned int)(image->pxw); > +unsigned int const height = (unsigned int)(image->pxh); > +unsigned int const rowstride = (unsigned int)(image->pxrs); > Geom::Point tp = p * image->grid2px; > -int const ix = (int)(tp[Geom::X]); > -int const iy = (int)(tp[Geom::Y]); > +unsigned int const ix = (unsigned int)(tp[Geom::X]); > +unsigned int const iy = (unsigned int)(tp[Geom::Y]); > > -if ((ix < 0) || (iy < 0) || (ix >= width) || (iy >= height)) > +if ((ix >= width) || (iy >= height)) > return NULL; > > -unsigned char *pix_ptr = pixels + iy * rowstride + ix * 4; > +unsigned char *pix_ptr = pixels + iy * rowstride + ix * 4U; > // is the alpha not transparent? > return (pix_ptr[3] > 0) ? item : NULL; also this patch even if sensible doesn't apply in 0.91 where that file doesn't even exist anymore... -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: [RFS] updated libva and intel-vaapi-driver bpos
On Tue, Sep 13, 2016 at 05:03:23PM -0400, Nicholas D Steeves wrote: > Does "Needs-Build" status mean > that the package is still waiting for CPU time on an armel, armhf, and > mipsel system somewhere on the buildd network? Yes, it's waiting for a spare buildd to pick up the builds. I don't know how the backports upload are considered in the build priority, but clearly not near the top¹.. ¹ e.g. I know that security builds are scheduled before anything else, then stable, then unstable, then experimental; and that within a single suite there are other things dictating priorities (like, new packages are built after updated ones, even if the latter came after). I just don't know where backports is in that list. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: [RFS] updated libva and intel-vaapi-driver bpos
On Mon, Sep 12, 2016 at 06:41:25AM +, Mattia Rizzolo wrote: > Given that I gather intel-vaapi-driver needs the newer libva and today > I'm too lazy to copy .deb in the local repository I'll wait for libva to > reach the mirror before doing intel-vaapi-driver. apparently amd64 is comparable to mipsel, as it's kinda lagging. https://buildd.debian.org/status/package.php?p=libva=jessie-backports I'm going to just trust you that it build and upload. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#837291: inkscape: use https for inkscape homepage
control: tag -1 pending On Sat, Sep 10, 2016 at 10:25:49AM +0200, Daniel Kahn Gillmor wrote: > Package: inkscape > Version: 0.91-10 > Severity: minor > Tags: patch > > Please use https for inkscape's homepage: Thanks, patch applied to git :) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#836596: libavutil55: borked NMUs with differing changelog
On Sun, Sep 04, 2016 at 10:50:36AM -0700, Daniel Schepler wrote: > OK, the "binary-only=yes" is what I missed. What I actually did was: > manually schroot into sid-x32-sbuild (after requesting buildd to shut > down temporarily); then extracted src:ffmpeg and src:chromaprint, > added the binNMU changelog manually for ffmpeg; then built and > installed ffmpeg with the stage1 build profile, built and installed > chromaprint, then did a full build of ffmpeg. umh, ok, that was a case where you needed to bootstrap ffmpeg, so maybe using sbuild'd --make-binNMU was not easily accomplished. Or peraphs you could have: 1) sbuild --make-binNMU="Manually built to resolve circular Build-Depends with chromaprint." --binNMU=3 --profile=stage1 2) upload those binaries somewhere accessible to the buildd (I think even uploading them to ports.d.o would have been ok) 3) schedule a regular binNMU without any build profile (maybe through wanna-build, even) I think that would have brought to the same result (module a higher binNMU version for the second build), with even less hassle :) (disclaimer: icbw, I'm not a porter, nor a bootstrapper) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#836596: libavutil55: borked NMUs with differing changelog
On Sun, Sep 04, 2016 at 07:45:07AM -0700, Daniel Schepler wrote: > On Sun, Sep 4, 2016 at 4:40 AM, Thorsten Glaser <t...@mirbsd.de> wrote: > > tglase@tglase:~ $ diff -u clog-* > > --- clog-i386 2016-08-28 12:12:00.0 +0200 > > +++ clog-x322016-09-03 16:36:00.0 +0200 > > @@ -1,3 +1,10 @@ > > +ffmpeg (7:3.1.3-1+b3) unstable; urgency=medium > > + > > + * Binary-only NMU: Rebuild against against libchromaprint1. > > + * Manually built to resolve circular Build-Depends with chromaprint. > > + > > + -- x32 Build Daemon (frobozz) > > <buildd_x32-frob...@buildd.debian-ports.org> Sat, 03 Sep 2016 07:36:24 > > -0700 > > + > > ffmpeg (7:3.1.3-1) unstable; urgency=medium > > > >* Team upload. > > Sorry about that, I did in fact have to do manual builds for the > reason mentioned (and it looks like essentially the same situation > still exists on hppa and sparc64). I thought the build system would > automatically separate out the binNMU log into > /usr/share/doc/*/changelog.x32.gz. It indeed happens automatically. What you did wrong is probably *how* that binNMU was scheduled. sbuild (and pbuilder too nowadays) have their options to do it, and they do it right, so I really wonder what you did, because yes, dpkg (=> the "build system" of yours above :)) splits automatically the binNMU changelog. You are missing the 'binary-only=yes' "option" on it; the first line should have been: ffpmeg (7:3.1.3-1+b3) unstable; urgency=low, binary-only=yes (or another urgency; the urgency field for binNMUs is pretty indifferent). > At this point, I can't really see any way to fix the issue, though > (short of scheduling another binNMU for all architectures). good question :) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#598791: inkscape: Bezier curves drawn, where svg file requires circular arcs
Control: tag -1 fixed-upstream On Tue, Aug 23, 2016 at 02:25:01PM +0200, Heinrich Schuchardt wrote: > The bug is fixed in Inkscape 0.92pre1 15071 oh, nice :) > Please, update the package when Inkscape 0.92 is released. Sure! :D Thanks for notifying us! -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: [SCM] xwax/master: Add bindnow hardening, disable pie for performance reasons
On Mon, Aug 22, 2016 at 08:39:29PM +0200, Jaromír Mikeš wrote: > I am enabling parallel build simply in d/rules file: > dh $@ --parallel That's the way it has to be done. (unless you're not using dh, but then you probably know your way) > I believe that number of processes is given by number of cores on > given server in this case. there is nothing such automagic (luckily). The level of parallelism is decided by the buildd administrator by exporting DEB_BUILD_OPTIONS=parallel=n, with n to its likings. n doesn't only depend on the number of cores. The total number of RAM has to be considered too, as well whether there are going to be any other build ongoing on the same system at the same time. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#627961: inkscape: rasterizing effects when exporting from the commandline
control: tag -1 moreinfo unreproducible As upstream wrote in the forwarded bug report 2 years ago: > > Version: 0.48.1-2 > > > > when exporting from the commandline to pdf, ps or eps it seems not to > > be possible to select to raster effects (…) > > Not reproduced with Inkscape 0.48.1 and current stable (Inkscape 0.48.3.1) > using a simple test file with a blurred circle: > command line export to PDF always exports filter effects rasterized > unless explicitly disabled with '--export-ignore-filters', as described > in the man page and in the release notes about the initial implementation > of cairo-based exports to PDF/PS/EPS [1]. With the simple test case, the > object from the SVG file is present in the PDF file with both export > methods (GUI, command line). > > > (…) but instead the effected objects are just left out from the export > > The identical file, with exactly the same export options as used in the > GUI? Odd. If objects are missing completely in the generated PDF, this > is very likely not a failure of exporting via command line (as opposed > to using the GUI), but due to hitting a memory limitation while > generating huge bitmaps in memory during the export (see bug #494115). > > Could you please attach a sample file which triggered the reported issue, > to allow further investigation? > > [1] > <http://wiki.inkscape.org/wiki/index.php/Release_notes/0.47#PDF.2C_PostScript.2C_and_EPS_export> furthermore, a lot changed from 0.48.x to 0.91.x, do you mind retesting? -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#829316: Updating the faac Uploaders list
Source: faac Version: 1.28+cvs20151130-1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Maia Kozheva <si...@ubuntu.com> has not been working on the faac package for quite some time. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#829314: Updating the smplayer Uploaders list
Source: smplayer Version: 16.4.0~ds0-1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Maia Kozheva <si...@ubuntu.com> has not been working on the smplayer package for quite some time. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#829315: Updating the smplayer-themes Uploaders list
Source: smplayer-themes Version: 1:15.12.0-1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Maia Kozheva <si...@ubuntu.com> has not been working on the smplayer-themes package for quite some time. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#829312: Updating the mjpegtools Uploaders list
Source: mjpegtools Version: 1:2.1.0+debian-4 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Maia Kozheva <si...@ubuntu.com> has not been working on the mjpegtools package for quite some time. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#829311: Updating the easytag Uploaders list
Source: easytag Version: 2.4.2-1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Maia Kozheva <si...@ubuntu.com> has not been working on the easytag package for quite some time. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#818201: kodi: Jasper removal
Hi Balint, On Tue, Mar 15, 2016 at 02:45:43PM +0100, Bálint Réczey wrote: > > Hi, jasper will be removed from Debian for the stretch release (and > > following that, the archive in general). > Kodi 17 wil not use jasper [1] and is expected to be release before > Stretch's freeze. > I plan fixing this bug with the 17.0 upstream release. Can you please fix it before? I see there is an alpha release avaialbe that should already contain that fix, or maybe backport the patch. In a few days kodi is going to be the very last blocker for jasper removal (as today I NMUed a bunch, and paved the way for the others). -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: swh-plugins_0.4.16+git20160531~repack0-2_amd64.changes REJECTED
On Wed, Jun 01, 2016 at 03:54:22PM +0200, Jaromír Mikeš wrote: > 2016-06-01 15:28 GMT+02:00 Mattia Rizzolo <mat...@debian.org>: > > 2. now there are stale files in the upload queue: > >ftp://ftp.upload.debian.org/pub/UploadQueue if any of them is broken > >your upload will fail. To remove them some DD has to `dcut rm` them. > > Ok. Can some DD do it please? done. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: swh-plugins_0.4.16+git20160531~repack0-2_amd64.changes REJECTED
On Wed, Jun 01, 2016 at 03:22:27PM +0200, Jaromír Mikeš wrote: > Any advice/help? Yes: 1. use dput instead of dupload (guess even better dput-ng, which does a hell more checks before the upload 2. now there are stale files in the upload queue: ftp://ftp.upload.debian.org/pub/UploadQueue if any of them is broken your upload will fail. To remove them some DD has to `dcut rm` them. 3. why are you uploading a -2? a -1 was never uploaded 4. if you upload -2 but never uploaded -1, use the -v option of dpkg-genchanges to include the -1 changelog in the changes, and so closing the bug closed in the -1 too. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#825045: groovebasin: please drop build-dep on node-stylus
Package: groovebasin Version: 1.4.0-1 Severity: serious Dear maintainer, the maintainer of node-css-parse requested the removal of the package in #764944, but that's currently blocked on node-stylus (#804509). Since apparently there is no real action on this front, I thik it would be sensible to just remove node-stylus too, and I'd like to proceed. The only rdep is groovebasin. Please remove the build-dep from it, or remove the package altogether. Thanks. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: RFS: audacious/3.6.2-2~bpo8+1 and audacious-plugins/3.6.2-2~bpo8+1
On Tue, May 10, 2016 at 06:03:18PM -0400, Nicholas D Steeves wrote: > > Now, umh, with `push debian/%(bpo_tag)s would be what I usually do > > without a branch. > > Ohhh, I think I'm starting to understand now. So what happens that > the local master branch gets ahead of the remote without --detach, but > that's ok. It's ok because git pushes a snapshot of the local changed > state to a remote state is only referenced by the tag. If for some > reason there was a bug in the debian/%(bpo_tag)s version, that's not > in the debian/version-revision...well, that's where it feels strange > to me. So then one would make further changes to the local repo, > local master would get further out of sync from remote master, but > that wouldn't matter because the local state of master is only ever > reflected as a tag on the remote? Well, you are not supposed to have your local master out of sync with the remote one. doing `git checkout debian/version-revision` detaches your head from a branch, and the stuff you do that are only referenced by the tag, yep. But if you do a `git checkout master` you ought to go back to the very place the remote master is, and doing stuff that means pushing to the remote master, and stuff pushed there is going to be on the next unstable upload. > Had I made my mistake at this > point, it seems like it would have been a huge mess! I see it's easy to do something wrong by accident here ;) > > given that now a branch is used instead the workflow is: > > This makes sense to me, but I'm still unclear why "git checkout > jessie-backports && git merge debian/version-revision" is preferred > over "git rebase debian/version-revision", when version-bumping the > bpo. I guess the question is: For a version bump of a bpo, should the > changelog of a new-version bpo mention the previous bpo, or should it > only contain a single "Rebuild for $stable-backports" entry? The "jessie-backports branch workflow" I keep as a reference is the one used by devscripts, that actually keeps the old backports entry in the changelog during the merge. > The > semantics of checkout+merge seem to favour a bpo changelog that > mentions prior versions (independent parallel branch with coherent > history and imported updates), while the semantics of git rebase seem > to favour a series of bpo forks (branch is a history of forks). my idea of bpo is a series of separated forks, and here detached tags work better than a branch. But I think this is really a matter of how you see it and how you work better, the actual thing doesn't really change much. > Mattia, thank you for taking the time to help me understand, > I appreciate it a lot, > Nicholas Sorry for making this actually simple backport look like a huge complicated deal :) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#823953: inkscape: PDF+Latex export completely broken
control: tag -1 upstream control: notfound -1 0.91-5~bpo8+1 control: found -1 0.91-5 control: forwarded -1 https://qbugs.launchpad.net/inkscape/+bug/1417470 On Tue, May 10, 2016 at 11:05:43AM -0600, Daniel Blaschke wrote: > Package: inkscape > Version: 0.91-5~bpo8+1 bpo bugs are not to be sent to the Debian BTS. But given that this issue actually affects also the regular release, tweaking the version. > see also the according launchbad bug report: > https://bugs.launchpad.net/ubuntu/+bug/1417470 So this is an upstream bug. Marking as so (but using the /inkscape/ part of the bug, instead of the ubuntu one. Also I added a Debian task to the LP bug, pointing to this very bug. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: RFS: audacious/3.6.2-2~bpo8+1 and audacious-plugins/3.6.2-2~bpo8+1
On Tue, May 10, 2016 at 03:17:30PM +, Mattia Rizzolo wrote: > So, I'm going to use a local bpo of sndio instead (also because yours > would not be nice to upload due to the +2. why 2 identical changelog > entries??), and try to build audacious again. Tomorrow first thing in > the morning most probably. Actually, already did and uploading now. Enjoy ;) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: RFS: audacious/3.6.2-2~bpo8+1 and audacious-plugins/3.6.2-2~bpo8+1
Sorry for the delay, these days are crazy for me On Fri, May 06, 2016 at 02:05:17PM -0400, Nicholas D Steeves wrote: > It seems I backported libsndio in a fugue state Feb 9th! I found a > libsndio-dev_1.0.1-2~bpo8+1_amd64.deb in my local repo. I can't find > an email notification from debian-mentors saying I uploaded it, so my > conclusion is that this was leftover cruft from when I just starting > out. You have my sincerest apologies. Nevermind, happens :) FTR, I tend to clean up my local repository as soon as I'm done with that build, as way too often happens to leave something there to me. > I've just purged that repo and uploaded a bpo of libsndio to mentors. mh, no. There is already one in bpo-NEW from 2 days ago :) https://ftp-master.debian.org/new/sndio_1.1.0-2~bpo8%2B1.html So, I'm going to use a local bpo of sndio instead (also because yours would not be nice to upload due to the +2. why 2 identical changelog entries??), and try to build audacious again. Tomorrow first thing in the morning most probably. > Message-ID: >
Re: RFS: audacious/3.6.2-2~bpo8+1 and audacious-plugins/3.6.2-2~bpo8+1
On Wed, May 04, 2016 at 11:32:20PM -0400, Nicholas D Steeves wrote: > /usr/include/roaraudio.h is found in libroar-dev. Libroar-dev is not > a build dependency of either a audacious or audacious-plugins; > likewise, libroar2 is not a runtime dependency. Have you added extra > packages to your clean chroot? definitely not. > A formal backport in a clean chroot+local repository so > audacious-plugins can build against the backported audacious worked > for me. > > https://mentors.debian.net/package/audacious-plugins > https://mentors.debian.net/package/audacious I tried now the very packages you uploaded there, and failed the same. Some things: root@chase:/build/audacious-plugins-3.7.2# ls /usr/include/libroar/libroar.h /usr/include/libroar/libroar.h root@chase:/build/audacious-plugins-3.7.2# dpkg -S /usr/include/libroar/libroar.h libroar-dev: /usr/include/libroar/libroar.h root@chase:/build/audacious-plugins-3.7.2# aptitude why libroar-dev i pbuilder-satisfydepends-dummy Depends libsndio-dev i A libroar-dev Provides libsndio-dev in sid there is a *real* libsndio-dev, but that package is not in jessie. Instead, in jessie the only thing providing that package is libroar-dev. Which rises the question: do *you* a clean chroot? My chroot is a simple jessie, + the jessie-bpo and the local repo added, and the only things installed from outside jessie are the binaries built by the locally backported audacious. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: RFS: audacious/3.6.2-2~bpo8+1 and audacious-plugins/3.6.2-2~bpo8+1
On Mon, May 02, 2016 at 08:50:55AM +, Mattia Rizzolo wrote: > I'll go ahead and built later. So, I've now actually tried to build them. src:audacious built just fine, but audacious-plugins failed: Entering directory sndio-ng. make[5]: Entering directory '/build/audacious-plugins-3.7.2/src/sndio-ng' make[6]: Entering directory '/build/audacious-plugins-3.7.2/src/sndio-ng' make[7]: Entering directory '/build/audacious-plugins-3.7.2/src/sndio-ng' make[7]: Leaving directory '/build/audacious-plugins-3.7.2/src/sndio-ng' Successfully generated dependencies. make[6]: Leaving directory '/build/audacious-plugins-3.7.2/src/sndio-ng' make[6]: Entering directory '/build/audacious-plugins-3.7.2/src/sndio-ng' In file included from /usr/include/libroar/libroar.h:153:0, from /usr/include/roaraudio.h:133, from /usr/include/libroarsndio/libroarsndio.h:52, from /usr/include/sndio.h:9, from sndio.cc:34: /usr/include/libroar/services.h:128:8: error: expected unqualified-id before 'new' int (*new)(const struct roar_audio_info * info, int dir, int parent, int mixer); ^ /usr/include/libroar/services.h:128:8: error: expected ')' before 'new' sndio.cc: In member function 'virtual bool SndioPlugin::open_audio(int, int, int)': sndio.cc:187:64: error: 'SIO_DEVANY' was not declared in this scope const char * device2 = device[0] ? (const char *) device : SIO_DEVANY; ^ Failed to compile sndio.cc (plugin)! ../../buildsys.mk:413: recipe for target 'sndio.plugin.o' failed make[6]: *** [sndio.plugin.o] Error 1 make[6]: Leaving directory '/build/audacious-plugins-3.7.2/src/sndio-ng' ../../buildsys.mk:116: recipe for target 'all' failed make[5]: *** [all] Error 2 make[5]: Leaving directory '/build/audacious-plugins-3.7.2/src/sndio-ng' ../buildsys.mk:123: recipe for target 'sndio-ng' failed make[4]: *** [sndio-ng] Error 2 make[4]: Leaving directory '/build/audacious-plugins-3.7.2/src' ../buildsys.mk:116: recipe for target 'all' failed make[3]: *** [all] Error 2 make[3]: Leaving directory '/build/audacious-plugins-3.7.2/src' buildsys.mk:123: recipe for target 'src' failed make[2]: *** [src] Error 2 make[2]: Leaving directory '/build/audacious-plugins-3.7.2' buildsys.mk:116: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/build/audacious-plugins-3.7.2' dh_auto_build: make -j1 returned exit code 2 debian/rules:20: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 So, I uploaded nothing. Nicholas: you still haven't confirmed that you are subscribed to the debian-backports@ ML, where eventual backport-related bugs should end up. Also, please check that build failure I got. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: RFS: audacious/3.6.2-2~bpo8+1 and audacious-plugins/3.6.2-2~bpo8+1
On Mon, May 02, 2016 at 09:34:05AM +0200, Mateusz Łukasik wrote: > The best way is creating jessie branch and prepare backport there. jessie-backports, no 'jessie', please (I renamed the branches already). The 'jessie' branch should be used for eventual stable updates. I saw you also renamed the tags. Well, thanks. I'll go ahead and built later. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: RFS: audacious/3.6.2-2~bpo8+1 and audacious-plugins/3.6.2-2~bpo8+1
On Fri, Apr 29, 2016 at 07:55:29PM -0400, Nicholas D Steeves wrote: > > I see you pushed to the master branch. This is wrong straigh away. > > The master branch is used to do the main development of the package, and > > targets either unstable or experimental. If you want to keep the > > backports stuff in a branch (as I think you could very well do), do it > > in a jessie-backports branch, not master. > > But you said you preferred it to be pushed with just a tag! yes, but not in master! A tag is always wanted in any case, with "just a tag" I was meaning a tag that is not in any branch, try having a look at some package of mine with a backport (like pbuilder, diffoscope, s3fs-fuse,...), you'll see that there is a bpo tag, but the commit referenced by that tag is not in any branch. But I can easily see how this can be confusing/hard, so a jessie-backports tag is just a very good way to deal with it! :) > So you wanted me to detach from the master branch with: git checkout > master^ before making changes? git checkout master^ would bring you to whatever is right before master (what's so special about the second-last commit on master?) You should make sure that you are on the commit describing the uploaded package, which not always is what is pointed by master. So probably here I'd say that you should do `git checkout debian/3.7.2-1` (or whatever version you are backporting) before doing anything > And when the next version of the package hits stable I'd git checkout > master && git checkout master^ ? erm? Can't understand what you mean here (1/ "hits stable" is very much something not real 2/ `git checkout master && git checkout master^` looks very fishy, what would do that?) > I'd be happy to take responsibility for my mistake, especially since > I'd like to learn to to fix it. According to the following guide I > should be able to do with with: > https://www.atlassian.com/git/tutorials/undoing-changes/git-checkout That would be mostly about undoing a particular change in a file in a subsequent commit. My question before was mostly aimed to the others members of the team, to know whether they like destroying history or not. In the first case a `git reset --hard 7c8a90` and `git push --force` (note that this might require more work, as non-fast-forward pushes are not usually allowed by the remote repos on alioth) should be enough. In the second, a `git revert a6274ea` will create another commit reverting the changes done after that commit specified, and pushed so. Just saying (as I'd like to hear from somebody else), if the first was done without deleting the tag, such tag would be the way I prefer them to be when dealing with backports :) > What tag would you like me to use for the backport? the tag should be 'debian/$version', so like 'debian/3.7.2-1_bpo8+1'. `gbp buildpackage` would create it right. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: RFS: audacious/3.6.2-2~bpo8+1 and audacious-plugins/3.6.2-2~bpo8+1
On Fri, Apr 29, 2016 at 01:07:20PM -0400, Nicholas D Steeves wrote: > I made my changes, git add, git commit, git tag. I wasn't sure which > convention to use for backports, so I based my tag on the debian > version. It's at the top of the list for git tag -l. I also wasn't > sure if I should if I should reset the tag back to the debian/3.7.2-1 > and debian/3.7.2-2. Please indicate how I can do a better job next > time. let's do it right this time too :), as you want to *maintain* the backport, you ought to learn it. I see you pushed to the master branch. This is wrong straigh away. The master branch is used to do the main development of the package, and targets either unstable or experimental. If you want to keep the backports stuff in a branch (as I think you could very well do), do it in a jessie-backports branch, not master. Now, the question about what to do with that commit arises. If this was a repository of mine I'd have just force-pushed it, but I won't do it here unless somebody says me to do it. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: RFS: audacious/3.6.2-2~bpo8+1 and audacious-plugins/3.6.2-2~bpo8+1
On Thu, Apr 07, 2016 at 08:26:28PM -0400, Nicholas D Steeves wrote: > I'm a member of the team, and I'd like to maintain backports of these > packages for Jessie. ok. > I > thought it was more appropriate to post here first, but please let me > know if you prefer an official RFS bug. It's appropriated here, yep :) Though, even if I routinely processes RFSes from the request-sponsorships pseudopackage, I usually just ignore RFS emails to random mailing lists unless i can do them right now. So, for what relates to me, I just skipped this. Though, there are several other people who can do it. Sebastians pinged me earlier to have a look at this :) > Would ctaylor, bilalakhtar, Cyril Lavier, or someone else please > sponsor this upload? I'll happilly do so, but I'd really prefer to do so over git, so please do your backporting on the git repositories of those 2 things, either in a jessie-backports branch, or just with a tag (I mean, I don't really see the point in such jessie-backports branches, I prefer to do my backports just with tags without them being on any branch, but this can be a bit hard to grasp if you are not used to use git, so do it as you prefer). Please poke me (as in: put my email in the To/Cc, so it gets in folder where i actually pay real attention to mails) once you are done, and I'll look at what you did and build/sign/upload :) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Ready for upload: guitarix, dgedit
On Mon, Mar 21, 2016 at 01:41:45PM +0100, Víctor Cuadrado Juan wrote: > Many thanks for the review! :) followed up on IRC and uploaded. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Ready for upload: guitarix, dgedit
On Mon, Mar 21, 2016 at 01:41:45PM +0100, Víctor Cuadrado Juan wrote: > On 16/03/16 16:53, Mattia Rizzolo wrote: > > On Wed, Mar 16, 2016 at 01:33:33PM +0100, Víctor Cuadrado Juan wrote: > > * d/changelog: > > + remove the line with the square brackets with your name, you are the > > only onw who made changes this time > > + remove that line wrt .pc in .gitignore, that's really a thing that > > won't impact the built package (nor the source) in any way > > + "fix ftbfs by moving to $(random package)", that's really > > incomprehensible. next time please run wrap-and-sort in a separate > > commit, and then change the build-deps. and rewrite that changelog > > line to read "Build-Depend on libwebkitgtk-dev instead of > > libwebkit-dev" or something similar, so it can be understood what > > have been done > > Fixed. > > > * d/copyright: > > + I'm pretty sure the copyright years of the upstream part need to be > > updated, you wrote 2008 but the first file I opened says 2010, I'm > > confident there are even more recent files. > > I have decided to drop the machine-readable copyright for now; it needs > too much work. I have updated the old d/copyright to reflect the > external copyrights and licenses that don't come from upstream's team > (and have their own readmes and licenses in their folders anyway). > Also, bumped it to 2016. Sad, but I see your point. Though you must have forgot to push, only the d/rules change it's there. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Ready for upload: guitarix, dgedit
On Wed, Mar 16, 2016 at 01:33:33PM +0100, Víctor Cuadrado Juan wrote: > Hi, Hi Victor! > I have 2 packages ready for upload[1], can someone please do it for me?: sure thing! but: > - dgedit: Minor debian-related changes. this commit: https://anonscm.debian.org/cgit/pkg-multimedia/dgedit.git/commit/?id=64f6a825ecf2a02c83298a5460e235634e4f6c63 you should read debhelper(7). You'll find that dh(1) and all of the dh_auto_* debhelper utilities already exports the build flags by dpkg, there is really no need to export them manually that way in d/rules. Can you please just remove those lines instead? > - guitarix: fixes FTBFS, migrates the package to the Debian Multimedia >Team, and maybe more importantly, frees the old maintainer from >possibly receiving email notifications. yay, finally I can do this in git :D * d/changelog: + remove the line with the square brackets with your name, you are the only onw who made changes this time + remove that line wrt .pc in .gitignore, that's really a thing that won't impact the built package (nor the source) in any way + "fix ftbfs by moving to $(random package)", that's really incomprehensible. next time please run wrap-and-sort in a separate commit, and then change the build-deps. and rewrite that changelog line to read "Build-Depend on libwebkitgtk-dev instead of libwebkit-dev" or something similar, so it can be understood what have been done * d/copyright: + I'm pretty sure the copyright years of the upstream part need to be updated, you wrote 2008 but the first file I opened says 2010, I'm confident there are even more recent files. > I made the error of git tagging them already, sorry for that :/. eheh, just delete them :) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: [SCM] giada/master: Set BUILD_DATE to date from debian/changelog
On Sun, Nov 15, 2015 at 07:09:02AM +0100, Jaromír Mikeš wrote: > 2015-11-06 22:39 GMT+01:00 <umlae...@users.alioth.debian.org>: > > The following commit has been merged in the master branch: > > commit 94c8da77170f65e46196fc97af5845629d22fb3c > > Author: IOhannes m zmölnig <zmoel...@umlautq.umlaeute.mur.at> > > Date: Fri Nov 6 22:00:34 2015 +0100 > > > > Set BUILD_DATE to date from debian/changelog > > > > diff --git a/debian/rules b/debian/rules > > index 48f2758..a7cc037 100755 > > --- a/debian/rules > > +++ b/debian/rules > > @@ -5,7 +5,9 @@ DEBIAN_DIR := $(shell echo ${MAKEFILE_LIST} | awk '{print > > $$1}' | xargs dirname > > UPSTREAM_VERSION ?=$(shell uscan --dehs | sed -n > > 's/.*\(.*\)<\/upstream-version>.*/\1/p') > > DFSG = dfsg1 > > PKG = $(shell dpkg-parsechangelog | sed -ne 's/^Source: //p') > > +DATE := $(shell date -u -d "$$(dpkg-parsechangelog -SDate)" +"%Y/%m/%d") > > > > +CPPFLAGS+=-DBUILD_DATE='"$(DATE)"' > > LDFLAGS+=-Wl,--as-needed > > Hi IOhannes, > > for what is this needed? Indeed the commit message lack that information, but it's needed to make the build reproducible, as the final d/changelog says: * Made build reproducible * Patch to allow setting of DATE in about-dialog * Set BUILD_DATE to date from debian/changelog -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#802164: inkscape: FTBFS on hppa since switch to gcc-5
On Tue, Oct 20, 2015 at 07:07:39PM +0100, Alex Valavanis wrote: > Hi All, > > Just a quick note that we're planning upstream to switch to require a > C++11 compliant compiler. This is needed for compatibility with new > versions of the GNOME development libraries. We'll hopefully switch > in time for Inkscape 0.92. cool! That would be great, indeed, so we have to do nothing special to our build rules. Furthermore, the inkscape currently in git brings quite some good, so I'd really welcome a new release. Do you have a wild timeframe for 0.92? -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#802164: inkscape: FTBFS on hppa since switch to gcc-5
[forwarding to the bug + relevant CC. @Alex: here in Debian we live with mails, sometime building up a big CC list :)] - Forwarded message from Alex Valavanis <valavanisa...@gmail.com> - Date: Tue, 20 Oct 2015 19:16:53 +0100 From: Alex Valavanis <valavanisa...@gmail.com> To: Mattia Rizzolo <mat...@mapreri.org> Subject: Re: Bug#802164: inkscape: FTBFS on hppa since switch to gcc-5 On 20 October 2015 at 19:11, Mattia Rizzolo <mat...@mapreri.org> wrote: > That would be great, indeed, so we have to do nothing special to our > build rules. Probably not... we'd most likely use an autoconf macro that will set a suitable build option with most common compilers. > Furthermore, the inkscape currently in git brings quite some good, so > I'd really welcome a new release. Do you have a wild timeframe for > 0.92? We're stepping up the frequency of releases. I'd guess at a couple of months for 0.92. We're aiming for a bug-fix release (0.91.1) sooner though, with a lot of backported patches from 0.92. There's a draft changelog here: http://wiki.inkscape.org/wiki/index.php/Release_notes/0.91.1 Best wishes, AV - End forwarded message - -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#802164: inkscape: FTBFS on hppa since switch to gcc-5]
[ another forward, sorry for breaking the threading probably a bounce would have been better, dunno... ] - Forwarded message from Mattia Rizzolo <mat...@mapreri.org> - Date: Tue, 20 Oct 2015 18:35:49 + From: Mattia Rizzolo <mat...@mapreri.org> To: Alex Valavanis <valavanisa...@gmail.com> Subject: Re: Bug#802164: inkscape: FTBFS on hppa since switch to gcc-5 User-Agent: Every email client sucks, this one just sucks less. On Tue, Oct 20, 2015 at 07:16:53PM +0100, Alex Valavanis wrote: > On 20 October 2015 at 19:11, Mattia Rizzolo <mat...@mapreri.org> wrote: > > Furthermore, the inkscape currently in git brings quite some good, so well s/git/bzr/ eheh > > I'd really welcome a new release. Do you have a wild timeframe for > > 0.92? > > We're stepping up the frequency of releases. I'd guess at a couple of > months for 0.92. We're aiming for a bug-fix release (0.91.1) sooner > though, with a lot of backported patches from 0.92. There's a draft > changelog here: > > http://wiki.inkscape.org/wiki/index.php/Release_notes/0.91.1 great, thanks for giving us some idea about how we should wait. now, back in topic, dear Dave, do you think it's enough for you to wait about a couple of months of the new upstream release? either that, or can you attach a patch to achive this that we'll rever as soon as 0.92 is out? - End forwarded message - -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#802164: inkscape: FTBFS on hppa since switch to gcc-5
On Sat, Oct 17, 2015 at 05:32:17PM -0400, John David Anglin wrote: > /usr/include/c++/5/bits/c++0x_warning.h:32:2: error: #error This file > requires compiler and library support for the ISO C++ 2011 standard. This > support is currently experimental, and must be enabled with the -std=c++11 or > -std=gnu++11 compiler options. > #error This file requires compiler and library support for the \ > ^ > > It appears -std=c++11 needs to be added to CXXFLAGS. umh, I'm quite naive when it comes to this matters, but isn't c++11 the default nowadays with g++5? Or does the hppa build of gcc default to something else? Then I also see quite some errors from glibmm-2.4, which is currently broken, so I'm not even sure inkscape is buildable at all atm due to that. https://bugs.debian.org/800371 (it's funny 'cause that bug actually link a inkscape build log!) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#798341: [inkscape] impossible to install inkscape
On Thu, Oct 15, 2015 at 07:12:16PM +, Diego Alejandro Agudelo España wrote: > > > > Maybe, but here inksacpe installed well on a testing system. You > > should check for foreign, maybe self-compiled packages: > > > > apt-show-versions | grep unknown > > > > and: > > > > apt-show-versions | grep 'No available version in archiv' > > > > > This finally solved my problem. Using 'apt-show-versions | grep 'No > available version in archiv'' I found out that somehow I had manually Oh, that command is really handy! Guess the next transition will be easier for me now ;) Thanks Klaus! > Thank you all for your help. Debian has a great community! Happy to see you made it :) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#798341: [inkscape] impossible to install inkscape
On Wed, Oct 14, 2015 at 11:03:25PM +, Diego Alejandro Agudelo España wrote: > First of all I want to apologize beforehand if I'm breaking any rule or > protocol for reporting bugs in Debian, it's the first time I'm > writing/reporting a problem here. > > I noticed that you marked this ticket as closed but after reading this > thread I'm still unable to install Inkscape in Debian testing. The error > message I got is similiar to the message reported by Marco Righi, which is: Indeed, let me assure you no bug is currently in place (well, at least this one is not), and that any support forum might be very well able to help you resolve this. Anyway, let me give you some hints and let's see whether we're able to sort it out. > The following packages have unmet dependencies: > inkscape : Depends: libatkmm-1.6-1v5 (>= 2.22.1) but it is not going to be > installed > Depends: libcairomm-1.0-1v5 (>= 1.6.4) but it is not going to be > installed > Depends: libglibmm-2.4-1v5 (>= 2.44.0) but it is not going to be > installed > Depends: libgtkmm-2.4-1v5 (>= 1:2.24.0) but it is not going to be > installed > Depends: libpangomm-1.4-1v5 (>= 2.36.0) but it is not going to be > installed > Depends: libsigc++-2.0-0v5 (>= 2.2.0) but it is not going to be > installed > E: Unable to correct problems, you have held broken packages. Ok, so according to you you don't have any other repository enabled. I can believe you: I hade several problems too, and I had to manually do something, even if I don't use any other external repository, that's because I had a locally built package that was blocking things. Another common case is a library that got manually installed for whatever reason: if that the case apt won't easily propose you a solution including removing them, while in this case might be needed. The workthrough I'm suggesting you to persue is: 1) try to tell apt to install all those package it does not want to install, other than installing the singular 2) if it still complain take one library per time still giving problems and force apt to install it 3) you'll arrive at some point where it propose you to remove some pacakages; this can mean either half of your system or a handful of packages 3a) if they are only a handful of leaf packages just remove them, you'll try reinstalling them later, once you resolved this other problem 3b) if it's half of the system then reand that list throughly, and look for "suspicious" packages, that means packages installed locally, manually built, coming from other repository you removed, and big leaf packages that might cause issues (I mean, "big" end-user applications, like sigil. Most probably the faulty package is also outdated. Ask apt to explicitely update it, or remove it. 4) goto 1 If everything is good I suggest you to mark as automatically installed every package other than inkscape itself, so that apt can be more ease with them and treat them as a real library, something that can come and go: $ sudo apt-mark auto $pkg1 $pkg2 $pkg3 $pkgN In my case I was in the 3b situation, reviewing that list made me notice a locally build scribus package, and some other stuff I just removed and fixed to get them back later on. It may look hard to do but trust me is not :) It just requires some time if you're not used to keep apt in your hands, but nothing to be scared about :) > Do you guys have any suggestion to fix this? > > I'm open to provide more details about my particular system configuration. Please try this and see where you end. Hopefully you'll find what is blocking you. I'd like to at least see whether I can help somebody keeping his system working... :) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#800878: inkscape: non-free file "gallardo.svgz"
On Mon, Oct 05, 2015 at 12:52:49AM +1100, Dmitry Smirnov wrote: > According to its metadata, image "/usr/share/inkscape/examples/gallardo.svgz" > appears to be non-free: > > WorkLicense: http://creativecommons.org/licenses/by-nc-sa/2.5/ > LicenseProhibits: http://web.resource.org/cc/CommercialUse > WorkDescription: A traced Lamborghini Gallardo. > The source image can be found at: > http://en.wikipedia.org/wiki/Image:Lamborghini_Gallardo_silver.jpg It's funny because according to that wikipedia page the image under a double license GFDL-1.2 / CC-BY-SA-3.0. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#733678: inkscape: Provide a -dbg package with debugging symbols
On Tue, Sep 15, 2015 at 07:26:52AM +0200, Bálint Réczey wrote: > I have already scheduled removing kodi's -dbg package with the next upload. note that you can't just drop manual debug packages, you need to provide an upgrade path from the manual ones to the automatic ones, otherwise user will run into installability/dependencies problems. That means using dh_strip --ddeb-migration="kodi-dbg << 15.1+dfsg1-4~" (or whatever version you'll use). See dh_strip(1). I would rather not add a manual -dbg just to avoid keeping such 2-lines for too long (while I'm struggling at removing uneeded stuff from the package). -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: Digital signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#733678: inkscape: Provide a -dbg package with debugging symbols
control: tags -1 - patch On Thu, May 14, 2015 at 05:29:14AM +0200, Roland Hieber wrote: > On Tue, 12 May 2015 20:41:36 +0200 Roland Hieber <roh...@rohieb.name> wrote: > > Ah, just realized that I replied to the wrong bug %-) This should be on > > #785141: > > Anyway, here is a patch that works for me. This patch is not enough, since after that the actual inkscape package will contain virtually nothing. Though I'm really uneasy at adding such a binary package while we are so close to the automatic debug packages (see [0] for more info). I'm somewhat tempted to mark this as wontfix and just wait some more weeks (yes, because currently it's really blocked on just few needed actions) [0] <55db88c9.4010...@thykier.net> for the last status on it; there are several more email in debian-devel@ -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: Digital signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#798341: [inkscape] impossible to install inkscape
On Wed, Sep 09, 2015 at 10:24:28AM +0200, IOhannes m zmölnig wrote: > On 2015-09-09 09:52, Marco Righi wrote: > [...] > > inkscape : Depends: libatkmm-1.6-1 (>= 2.22.1) but it is not going to > > be installed > > in the past few weeks, Debian has seen a major transition (of the core > components for any C++-related software in Debian) that affected *many* > packages and included the renaming of some dependencies of inkscape. > only within the last days, this big change started migrating from > "unstable" to "testing". > > this basically means big disruption which should eventually go away > "automatically", once all packages have been transitioned from unstable > to testing. Though in a clean stretch chroot it does install. > i also see that you are running a mixed jessie/stretch (aka > "stable/testing") system, which i don't think is supported at all (i > think that one of the reasons for this is exactly because it is > impossible to support working systems that depend on a state both > *before* and *after* such big transitions we are currently seeing). This could very well be the cause, if it's not only the reposiotory precence but the system is actually hibryd. Also try with something like # apt-get install inkscape -t testing or # apt-get install inkscape -t stretch -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: Digital signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#795823: blender: Uninstallable in sid
On Tue, Sep 08, 2015 at 12:33:34AM +0200, Schiavon wrote: > Source: blender > Version: 2.74+dfsg0-4+b2 > Followup-For: Bug #795823 > > Dear Maintainer, > > I found blender uninstallable in debian Sid. I think it is also related > to the transition to GCC5, since it involves libopencolorio1 and > libopenimageio1.5v5 (which depends from libopencolorio1v5, in conflict > with libopencolorio1). > > I report here the message obtained when trying to install blender: > > "I seguenti pacchetti hanno dipendenze non soddisfatte: > blender : Dipende: libopencolorio1 ma non sta per essere installato >Dipende: libopenimageio1.5v5 ma non sta per essere installato > E: Impossibile correggere i problemi, ci sono pacchetti danneggiati bloccati." Please keep in mind that this is the Debian BTS. Most of the people reading this can't understand Italian, so you're always better at reporting erros in English. A way to do this is to put 'LC_ALL=C.UTF-8' (or just 'LC_ALL=C') right before the command you're invoking, for example LC_ALL=C.UTF-8 apt install blender Anyway, this particular problem is due to libopenimageio1.5v5 depending on libopencolorio1v5 but blender depending on libopencolorio1, which clearly conflicts with the v5 variant. This is wow, I guess another blender rebuild is in order to fix this. @Matteo can you take care of this? I fail to see the transition trackers of those two libs above, so I have no clue where they are tracked... -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: Digital signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers