Bug#773329: Incorrect Cflags line in jack.pc
On 04/19/2015 09:10 AM, Adrian Knoth wrote:
The cflags from pkg-config for jack are incorrect which breaks makefiles
and configure scripts that depend on them (e.g. those for rosegarden).
I tend to disagree - more likely, rosegarden is broken, because a ton of
other software that relies on jackd compiles just fine.
It appears that the issue is that rosegarden is using
PKG_CHECK_MODULES() when it should be using AC_CHECK_LIB(). I just
tried AC_CHECK_LIB() and it works fine. I'll get it into the next
release of rosegarden.
Cflags: -I/usr/include
...should be this:
Cflags: -I${includedir} -I${includedir}/jack
No, -I/usr/include is correct, because the appropriate include is
#include jack/jack.h
I thought this too, but actually the issue is a quirk in the way
pkg-config works. The Cflags line in the .pc file has to follow a very
specific and strange format (shown above) for PKG_CHECK_MODULES() to
work. It's really quite bizarre and perplexing. AC_CHECK_LIB() is much
more reliable.
So wontfix?
I agree.
___
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: Packaging ardour 4.0
2015-04-20 16:07 GMT+02:00 Fabian Greffrath fab...@greffrath.com: Am Montag, den 20.04.2015, 15:49 +0200 schrieb Adrian Knoth: No, I think lintian is wrong here. I have a HiDPI display (2560x1600 on 13 screen), and small icons are a pain. OSX (the only OS that has properly working HiDPI out of the box) ships icons up to 1024x1024, so lintian's 32x32 restriction is a total joke. This only applies to the Debian menu, i.e. the menu organized by the debian/*.menu files. This still needs 32x32 icons in XPM format. This does not affect the icons that are displayed e.g. in Gnome Shell. Is it already possible to have SVG logos? Yes, for .desktop files, i.e. the ones that are used to show icons in e.g. Gnome Shell, you can use SVG graphics or high-res PNG graphics. So we can have 2 icons 48x48 for desktop file and 32x32 for menu file if I understand right. regards mira ___ 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#783037: marked as done (xbmc: please package kodi and update the package)
Your message dated Tue, 21 Apr 2015 01:40:11 +0200 with message-id 55358e5b.3060...@googlemail.com and subject line Re: Bug#783037: xbmc: please package kodi and update the package has caused the Debian Bug report #783037, regarding xbmc: please package kodi and update the package to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 783037: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783037 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xbmc Version: 2:13.2+dfsg1-4 Severity: wishlist Dear Maintainer, The upstream have renamed it to 'kodi'. See http://kodi.tv/introducing-kodi-14/ and development is at https://github.com/xbmc/ . It does tell the way how to do the packaging as well at https://github.com/xbmc/xbmc/blob/master/tools/Linux/packaging/README.debian . Can somebody share why xbmc hasn't been updated yet ? Lack of time or something more serious ? -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (600, 'testing'), (500, 'testing-updates'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xbmc depends on: ii fonts-dejavu-core 2.34-1 ii fonts-roboto 1:4.4.4r2-6 ii libjs-iscroll 5.1.2+dfsg1-1 ii libjs-jquery 1.7.2+dfsg-3.2 ii mesa-utils 8.2.0-1 ii python-imaging 2.6.1-2 pn python:any none ii ttf-dejavu-core2.34-1 ii x11-utils 7.7+2 ii xbmc-bin 2:13.2+dfsg1-4 xbmc recommends no packages. xbmc suggests no packages. -- no debconf information -- Shirish Agarwal, Community Lead, Hamaralinux.org ---End Message--- ---BeginMessage--- Hi shirish, On 21.04.2015 01:04, shirish wrote: The upstream have renamed it to 'kodi'. See http://kodi.tv/introducing-kodi-14/ and development is at https://github.com/xbmc/ . It does tell the way how to do the packaging as well at https://github.com/xbmc/xbmc/blob/master/tools/Linux/packaging/README.debian . Can somebody share why xbmc hasn't been updated yet ? Lack of time or something more serious ? Kodi is already packaged [1] and has been waiting in the NEW queue for more than 3 months [2]. Meanwhile you can build it from git [3], or use Bálint's repository [4]. Best regards, Andreas 1: https://bugs.debian.org/767180 2: https://ftp-master.debian.org/new/kodi_14.0+dfsg1-1.html 3: https://anonscm.debian.org/cgit/pkg-multimedia/kodi.git 4: https://people.debian.org/~rbalint/ppa/xbmc-ffmpeg/---End Message--- ___ 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: Packaging ardour 4.0
2015-04-20 15:49 GMT+02:00 Adrian Knoth a...@drcomp.erfurt.thur.de: On 04/20/15 15:09, Jaromír Mikeš wrote: Great! How do you do repacking? Manually? Sort of. I track upstream git and then drop the waf binary. I wish the filter statement in gbp.conf would work, but for some reason it doesn't. P: ardour3 source: source-contains-autogenerated-visual-c++-file MSVCvst_scan/vst_scan.rc.in http://vst_scan.rc.in P: ardour3 source: source-contains-autogenerated-visual-c++-file MSVCvst_scan/resource P: ardour3 source: source-contains-autogenerated-visual-c++-file MSVCardour3/resource P: ardour3 source: source-contains-autogenerated-visual-c++-file icons/win32/resource P: ardour3 source: source-contains-autogenerated-visual-c++-file icons/win32/msvc_resources.rc.in http://msvc_resources.rc.in These should indeed be dropped. If you can figure out some magic to do this automatically, that would be great. There's automatic git-upstream-repackaging in CDBS, I've used it for jackd2, so taking a look at jackd2's debian/rules should get you started. I am using get-orig-source in rules file Recently I've used repacking from git in ntk package ... you can have a look for inspiration. I will have a look on copyright file later ... now busy Thanks, that's clearly an area I don't like to bother with at all, but I understand its importance. I updated a bit copyright file ... mostly just dropped files which has been dropped upstream too. So there will be second run to add file which has been added upstream ;) At least lintian yield less wild output now. regards mira ___ 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#783037: xbmc: please package kodi and update the package
Package: xbmc Version: 2:13.2+dfsg1-4 Severity: wishlist Dear Maintainer, The upstream have renamed it to 'kodi'. See http://kodi.tv/introducing-kodi-14/ and development is at https://github.com/xbmc/ . It does tell the way how to do the packaging as well at https://github.com/xbmc/xbmc/blob/master/tools/Linux/packaging/README.debian . Can somebody share why xbmc hasn't been updated yet ? Lack of time or something more serious ? -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (600, 'testing'), (500, 'testing-updates'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xbmc depends on: ii fonts-dejavu-core 2.34-1 ii fonts-roboto 1:4.4.4r2-6 ii libjs-iscroll 5.1.2+dfsg1-1 ii libjs-jquery 1.7.2+dfsg-3.2 ii mesa-utils 8.2.0-1 ii python-imaging 2.6.1-2 pn python:any none ii ttf-dejavu-core2.34-1 ii x11-utils 7.7+2 ii xbmc-bin 2:13.2+dfsg1-4 xbmc recommends no packages. xbmc suggests no packages. -- no debconf information -- Shirish Agarwal, Community Lead, Hamaralinux.org ___ 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: Packaging ardour 4.0
2015-04-19 14:13 GMT+02:00 Adrian Knoth a...@drcomp.erfurt.thur.de: Just wanted to let you know that I'm mostly done with packaging ardour4.0 (released yesterday). Hi Adrian, I gave a little test to Ardour4 ... looks really great. Just one issue I can't create session connected via ALSA with JACK it works as expected. Does it work for you? mira ___ 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: Packaging ardour 4.0
On 04/20/15 13:05, Jaromír Mikeš wrote: $ git checkout alioth/upstream-a4 $ git checkout -b upstream-a4 At least my version of git doesn't require the first line. Now I am building new ardour ... just noticed this in build output * Use External Libraries: False Does it mean that we use build-in libraries? Thanks for spotting this, fixed now. Just git pull. Cheers ___ 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: Packaging ardour 4.0
2015-04-20 14:36 GMT+02:00 Adrian Knoth a...@drcomp.erfurt.thur.de: On 04/20/15 13:05, Jaromír Mikeš wrote: $ git checkout alioth/upstream-a4 $ git checkout -b upstream-a4 At least my version of git doesn't require the first line. Now I am building new ardour ... just noticed this in build output * Use External Libraries: False Does it mean that we use build-in libraries? Thanks for spotting this, fixed now. Just git pull. Great! How do you do repacking? Manually? P: ardour3 source: source-contains-autogenerated-visual-c++-file MSVCvst_scan/vst_scan.rc.in P: ardour3 source: source-contains-autogenerated-visual-c++-file MSVCvst_scan/resource P: ardour3 source: source-contains-autogenerated-visual-c++-file MSVCardour3/resource P: ardour3 source: source-contains-autogenerated-visual-c++-file icons/win32/resource P: ardour3 source: source-contains-autogenerated-visual-c++-file icons/win32/msvc_resources.rc.in Should we ship smaller icon? E: ardour3: menu-icon-too-big usr/share/pixmaps/ardour4.xpm: 48x48 32x32 I will have a look on copyright file later ... now busy regards mira ___ 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: Packaging ardour 4.0
2015-04-19 22:28 GMT+02:00 Adrian Knoth a...@drcomp.erfurt.thur.de:
On 04/19/15 19:31, Jaromír Mikeš wrote:
I'm currently building in pbuilder and will report back later.
Amazing! I am excited to give it a try. ;)
Pushed to ardour3.git now, just checkout the master-a4 and upstream-a4
branches.
I am still not well familiar with branches
$ git checkout alioth/master-a4
$ git checkout alioth/upstream-a4
$ git-buildpackage --git-pbuilder --git-dist=sid --git-pristine-tar
$ gbp:error: Currently not on a branch
$ git checkout alioth/master-a4
HEAD is now at e421097... Set gbp.conf to {master,upstream}-a4
What is wrong ? :(
mira
___
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: Packaging ardour 4.0
On 2015-04-20 12:13, Jaromír Mikeš wrote: 2015-04-20 10:30 GMT+02:00 Fabian Greffrath fab...@greffrath.com: Am Montag, den 20.04.2015, 10:27 +0200 schrieb Jaromír Mikeš: What is wrong ? :( I think you will have to pass --git-debian-branch=master-a4 and --git-upstream-branch=upstream-a4 to gbp buildpackage to point it to the right branches. Sorry some problem between my ears , but still can't get it work. :( $ git checkout alioth/upstream-a4 is alioth/upstream-a4 a local branch? or is it just a short-form for the upstream-a4 branch on the alioth remote? if you see: $ git branch * (detached from alioth/upstream-a4) then you most likely have the 2nd case, and gbp seems to need a local branch. so do, e.g. $ git checkout upstream-a4 to create a local branch from the remote. apart from that, i would think that the branch foo/bar (as checked out) and the branch bar (as given to gbp) are never the same. fgmsdr IOhannes ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: tagging 773993
Processing commands for cont...@bugs.debian.org: # fixed in b183468 tags 773993 + fixed-upstream Bug #773993 [libavcodec56] avprobe loops endlessly on certain FLAC files Added tag(s) fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 773993: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773993 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ 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: Packaging ardour 4.0
Quoting Adrian Knoth (2015-04-20 11:30:50) On 04/19/15 14:13, Adrian Knoth wrote: Last not least, we should probably cut down on the number of ardour versions in Debian. Nobody supports a2 anymore, same for a3. It's a Would it make sense to exclude a2 from Jessie? Removal request? I wonder if it's possible to reintroduce a package without the epoch field by removing it first everywhere. Assuming it is not installed in jessie, one wouldn't need to worry about version comparison later. The way an epoch could be dropped is by 1) removing the package completely from Debian, 2) wait for two full stable release cycles (or arguably only one), and then 3) reintroduce the package again. Or am I too concerned about the epoch number? I believe so, yes. They are a minor cosmetic nuisance, and may (because of being rare) cause errors in package dependencies, but should not be considered broken in itself. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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: Packaging ardour 4.0
On Mon, Apr 20, 2015 at 12:13:17PM +0200, Jaromír Mikeš wrote:
Am Montag, den 20.04.2015, 10:27 +0200 schrieb Jaromír Mikeš:
What is wrong ? :(
I think you will have to pass --git-debian-branch=master-a4 and
--git-upstream-branch=upstream-a4 to gbp buildpackage to point it to
the right branches.
Sorry some problem between my ears , but still can't get it work. :(
$ git checkout alioth/upstream-a4
Previous HEAD position was e421097... Set gbp.conf to {master,upstream}-a4
HEAD is now at f3b3893... Imported Upstream version 4.0~dfsg
You're not creating a branch here. You either want
$ git checkout upstream-a4
which should do it automatically, or throw in a -b.
Cheers
--
mail: a...@thur.de http://adi.thur.de PGP/GPG: key via keyserver
___
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: Packaging ardour 4.0
Am Montag, den 20.04.2015, 11:23 +0200 schrieb Adrian Knoth: I've done that already, so it must be something else: You will have to be on the master-a4 branch already for this to take effect, which Jaromir probably wasn't. - Fabian ___ 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: Packaging ardour 4.0
2015-04-20 10:30 GMT+02:00 Fabian Greffrath fab...@greffrath.com:
Am Montag, den 20.04.2015, 10:27 +0200 schrieb Jaromír Mikeš:
What is wrong ? :(
I think you will have to pass --git-debian-branch=master-a4 and
--git-upstream-branch=upstream-a4 to gbp buildpackage to point it to
the right branches.
Sorry some problem between my ears , but still can't get it work. :(
$ git checkout alioth/upstream-a4
Previous HEAD position was e421097... Set gbp.conf to {master,upstream}-a4
HEAD is now at f3b3893... Imported Upstream version 4.0~dfsg
$ git checkout alioth/master-a4
Previous HEAD position was f3b3893... Imported Upstream version 4.0~dfsg
HEAD is now at e421097... Set gbp.conf to {master,upstream}-a4
$ git-buildpackage --git-debian-branch=master-a4
--git-upstream-branch=upstream-a4
gbp:error: Currently not on a branch
mira
___
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: Packaging ardour 4.0
2015-04-20 12:31 GMT+02:00 Adrian Knoth a...@drcomp.erfurt.thur.de:
On Mon, Apr 20, 2015 at 12:13:17PM +0200, Jaromír Mikeš wrote:
Am Montag, den 20.04.2015, 10:27 +0200 schrieb Jaromír Mikeš:
What is wrong ? :(
I think you will have to pass --git-debian-branch=master-a4 and
--git-upstream-branch=upstream-a4 to gbp buildpackage to point it to
the right branches.
Sorry some problem between my ears , but still can't get it work. :(
$ git checkout alioth/upstream-a4
Previous HEAD position was e421097... Set gbp.conf to
{master,upstream}-a4
HEAD is now at f3b3893... Imported Upstream version 4.0~dfsg
You're not creating a branch here. You either want
$ git checkout upstream-a4
which should do it automatically, or throw in a -b.
Thanks ... I finally got it hopefully right
$ git checkout alioth/upstream-a4
$ git checkout -b upstream-a4
$ git checkout alioth/master-a4
$ git checkout -b master-a4
Now I am building new ardour ... just noticed this in build output
* Use External Libraries: False
Does it mean that we use build-in libraries?
regards
mira
___
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: Packaging ardour 4.0
Am Montag, den 20.04.2015, 10:27 +0200 schrieb Jaromír Mikeš: What is wrong ? :( I think you will have to pass --git-debian-branch=master-a4 and --git-upstream-branch=upstream-a4 to gbp buildpackage to point it to the right branches. - Fabian ___ 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: Packaging ardour 4.0
On 04/20/15 10:45, Jonas Smedegaard wrote: What is wrong ? :( I think you will have to pass --git-debian-branch=master-a4 and --git-upstream-branch=upstream-a4 to gbp buildpackage to point it to the right branches. Right. The proper thing to do is for the person choosing to use non-default branch names to declare the chosen branch names in debian/gpb.conf. I've done that already, so it must be something else: http://anonscm.debian.org/cgit/pkg-multimedia/ardour3.git/commit/?h=master-a4id=e42109787c0bc239c645c2c0ace132ceb3d1fef6 Cheers ___ 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: Packaging ardour 4.0
On 20 April 2015 at 10:49, Adrian Knoth a...@drcomp.erfurt.thur.de wrote: On 04/20/15 15:09, Jaromír Mikeš wrote: Great! How do you do repacking? Manually? Sort of. I track upstream git and then drop the waf binary. I wish the filter statement in gbp.conf would work, but for some reason it doesn't. P: ardour3 source: source-contains-autogenerated-visual-c++-file MSVCvst_scan/vst_scan.rc.in http://vst_scan.rc.in P: ardour3 source: source-contains-autogenerated-visual-c++-file MSVCvst_scan/resource P: ardour3 source: source-contains-autogenerated-visual-c++-file MSVCardour3/resource P: ardour3 source: source-contains-autogenerated-visual-c++-file icons/win32/resource P: ardour3 source: source-contains-autogenerated-visual-c++-file icons/win32/msvc_resources.rc.in http://msvc_resources.rc.in These should indeed be dropped. If you can figure out some magic to do this automatically, that would be great. There's automatic git-upstream-repackaging in CDBS, I've used it for jackd2, so taking a look at jackd2's debian/rules should get you started. E: ardour3: menu-icon-too-big usr/share/pixmaps/ardour4.xpm: 48x48 32x32 Should we ship smaller icon? No, I think lintian is wrong here. I have a HiDPI display (2560x1600 on 13 screen), and small icons are a pain. OSX (the only OS that has properly working HiDPI out of the box) ships icons up to 1024x1024, so lintian's 32x32 restriction is a total joke. This is not lintian's restriction. The debian menu spec demands 32x32 icons: https://lintian.debian.org/tags/menu-icon-too-big.html I would not really bother with a menu file if ardour ships a .desktop entry. Is it already possible to have SVG logos? I believe the .desktop spec allows svg. The debian menu spec doesn't. -- Saludos, Felipe Sateler ___ 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: Packaging ardour 4.0
Am Montag, den 20.04.2015, 15:49 +0200 schrieb Adrian Knoth: These should indeed be dropped. If you can figure out some magic to do this automatically, that would be great. There's automatic git-upstream-repackaging in CDBS, I've used it for jackd2, so taking a look at jackd2's debian/rules should get you started. You should be able to use Files-Excluded in debian/copyright in conjunction with uscan: https://wiki.debian.org/UscanEnhancements No, I think lintian is wrong here. I have a HiDPI display (2560x1600 on 13 screen), and small icons are a pain. OSX (the only OS that has properly working HiDPI out of the box) ships icons up to 1024x1024, so lintian's 32x32 restriction is a total joke. This only applies to the Debian menu, i.e. the menu organized by the debian/*.menu files. This still needs 32x32 icons in XPM format. This does not affect the icons that are displayed e.g. in Gnome Shell. Is it already possible to have SVG logos? Yes, for .desktop files, i.e. the ones that are used to show icons in e.g. Gnome Shell, you can use SVG graphics or high-res PNG graphics. Cheers, Fabian PS: Please don't do version numbering stunts just to get rid of the epoch, it's really not worth the trouble. ;) ___ 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: Packaging ardour 4.0
Am Montag, den 20.04.2015, 14:36 +0200 schrieb Adrian Knoth: On 04/20/15 13:05, Jaromír Mikeš wrote: $ git checkout alioth/upstream-a4 $ git checkout -b upstream-a4 $ git fetch origin upstream-a4:upstream-a4 master-a4:master-a4 should do about the same. - Fabian ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Hello dear God Bless you, my name is Mrs.Roseanna I want to donate some fund which I inherited from my late husband to establish a charity foundation in your country under your care for the poor and l
___ 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: Packaging ardour 4.0
On 04/20/15 15:09, Jaromír Mikeš wrote: Great! How do you do repacking? Manually? Sort of. I track upstream git and then drop the waf binary. I wish the filter statement in gbp.conf would work, but for some reason it doesn't. P: ardour3 source: source-contains-autogenerated-visual-c++-file MSVCvst_scan/vst_scan.rc.in http://vst_scan.rc.in P: ardour3 source: source-contains-autogenerated-visual-c++-file MSVCvst_scan/resource P: ardour3 source: source-contains-autogenerated-visual-c++-file MSVCardour3/resource P: ardour3 source: source-contains-autogenerated-visual-c++-file icons/win32/resource P: ardour3 source: source-contains-autogenerated-visual-c++-file icons/win32/msvc_resources.rc.in http://msvc_resources.rc.in These should indeed be dropped. If you can figure out some magic to do this automatically, that would be great. There's automatic git-upstream-repackaging in CDBS, I've used it for jackd2, so taking a look at jackd2's debian/rules should get you started. E: ardour3: menu-icon-too-big usr/share/pixmaps/ardour4.xpm: 48x48 32x32 Should we ship smaller icon? No, I think lintian is wrong here. I have a HiDPI display (2560x1600 on 13 screen), and small icons are a pain. OSX (the only OS that has properly working HiDPI out of the box) ships icons up to 1024x1024, so lintian's 32x32 restriction is a total joke. Is it already possible to have SVG logos? I will have a look on copyright file later ... now busy Thanks, that's clearly an area I don't like to bother with at all, but I understand its importance. Cheers ___ 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: Packaging ardour 4.0
Quoting Adrian Knoth (2015-04-20 15:49:41) On 04/20/15 15:09, Jaromír Mikeš wrote: E: ardour3: menu-icon-too-big usr/share/pixmaps/ardour4.xpm: 48x48 32x32 Should we ship smaller icon? No, I think lintian is wrong here. I have a HiDPI display (2560x1600 on 13 screen), and small icons are a pain. OSX (the only OS that has properly working HiDPI out of the box) ships icons up to 1024x1024, so lintian's 32x32 restriction is a total joke. echo 'E: ardour3: menu-icon-too-big' | lintian-info E: ardour3: menu-icon-too-big N: N: Icons in the Debian menu system should be at most 32x32 pixels N: (icon16x16 icons should of course be at most 16x16 pixels) N: N: Refer to Debian Menu System section 3.7 (The icon field) for details. N: N: Severity: important, Certainty: certain N: N: Check: menu-format, Type: binary N: /usr/share/doc/menu/menu.txt.gz If menu policy is a joke, then please consider file a bugreport. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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: Packaging ardour 4.0
On 20 April 2015 at 11:57, Jonas Smedegaard d...@jones.dk wrote: Quoting Adrian Knoth (2015-04-20 15:49:41) On 04/20/15 15:09, Jaromír Mikeš wrote: E: ardour3: menu-icon-too-big usr/share/pixmaps/ardour4.xpm: 48x48 32x32 Should we ship smaller icon? No, I think lintian is wrong here. I have a HiDPI display (2560x1600 on 13 screen), and small icons are a pain. OSX (the only OS that has properly working HiDPI out of the box) ships icons up to 1024x1024, so lintian's 32x32 restriction is a total joke. echo 'E: ardour3: menu-icon-too-big' | lintian-info E: ardour3: menu-icon-too-big N: N: Icons in the Debian menu system should be at most 32x32 pixels N: (icon16x16 icons should of course be at most 16x16 pixels) N: N: Refer to Debian Menu System section 3.7 (The icon field) for details. N: N: Severity: important, Certainty: certain N: N: Check: menu-format, Type: binary N: /usr/share/doc/menu/menu.txt.gz If menu policy is a joke, then please consider file a bugreport. No need to file a new one, we already have one that was escalated to the tech-ctte. See policy bug 707851 and tech-ctte bug 741573 if you want the details. -- Saludos, Felipe Sateler ___ 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: Packaging ardour 4.0
Quoting Felipe Sateler (2015-04-20 17:06:25) On 20 April 2015 at 11:57, Jonas Smedegaard d...@jones.dk wrote: Quoting Adrian Knoth (2015-04-20 15:49:41) On 04/20/15 15:09, Jaromír Mikeš wrote: E: ardour3: menu-icon-too-big usr/share/pixmaps/ardour4.xpm: 48x48 32x32 Should we ship smaller icon? No, I think lintian is wrong here. I have a HiDPI display (2560x1600 on 13 screen), and small icons are a pain. OSX (the only OS that has properly working HiDPI out of the box) ships icons up to 1024x1024, so lintian's 32x32 restriction is a total joke. […] If menu policy is a joke, then please consider file a bugreport. No need to file a new one, we already have one that was escalated to the tech-ctte. See policy bug 707851 and tech-ctte bug 741573 if you want the details. Thanks for sharing! - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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
Processed: tagging 781812
Processing commands for cont...@bugs.debian.org: tags 781812 + fixed-upstream Bug #781812 [libav] Set AV_DISPOSITION_ATTACHED_PIC for MKV Cover Art Added tag(s) fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 781812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781812 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
