Re: Packaging ardour 4.0

[Debian/GNU]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 2015-09-21 10:54, IOhannes m zmölnig (Debian/GNU) wrote:
> On 2015-09-20 11:25, Jaromír Mikeš wrote:
 i simply see no reason to keep ardour3 around, and it has a
 crasher bug (#778363) triggered by loading any MIDI file (i
 think that should be raised to "important").
>>> 
>>> I would remove it.
> 
> i'd like to hear adrian on this first.

ping.

the question i would like you (adrian) to comment on is:
? shouldn't we request a removal of "ardour3" *now*?

fgmasdr
IOhannes
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWA8lxAAoJELZQGcR/ejb42IcP/0q/ZLYlTyY4JrdAiqrwpXeX
WMXlQFgOo78bDkxBw73mDpQ1PXC66v30UohHxjnVsuafewUp73suITKRYTAWBeVd
40sP+IKzUyi0RjrnwHF5Adum/9gEcrqAgK/I7lwasfLFWCBabn2wuR4a39ywzE+u
KEoATA2VWVg9EvuFKpnhrIiuYA0QHdJzCJOIPlrQcJU21R1xw7mrbQWYmde4cZIl
K/NhB21334EzitpHaAf1be/iHhSW68QL/fOn865ehHvGkTNPn9ntTaYE5PA2iD3s
0MOxcuF0/5aaRbC9WecMRkiqvvXNy9KWvelR9PJBkk/Sdf6f65b0hQfmxIlVT80C
jXKhMzn2Bux6qZhRtYgfWUEXakBXRYO7GhhQjkdImY/a/jCBBqM4JscUYKFA05xh
u1bRjGXrzfc80dHRwSPvPw94iRGfYvKmUzMYqkh8yahJQHV55LM3ie7Qy+VKXqMR
Xgb6/DTOdq3QGeeNt+Lct+21ZBL3cKtVGWNtNO7S2G4MuQWYB5yJ8oREiouqwwiU
4MaEd10ufUAMhUtbytZzZR+UPRjlP9BTtlfq7NrGGHTJALrGKcFWlIrPzChfzkLQ
oHzRgCkscaMrL8srxZf/yIW8BouOmNIa5fNi+LjZVFdZbgxDduBYcf0Ij81lZ/72
POEM+QrK/RqiGgoIv5gE
=zCoT
-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: Packaging ardour 4.0

[Adrian Knoth]

On Thu, Sep 24, 2015 at 11:59:17AM +0200, IOhannes m zmölnig (Debian/GNU) wrote:

>  i simply see no reason to keep ardour3 around, and it has a
>  crasher bug (#778363) triggered by loading any MIDI file (i
>  think that should be raised to "important").
> >>> 
> >>> I would remove it.
> > 
> > i'd like to hear adrian on this first.
> ping.
> 
> the question i would like you (adrian) to comment on is:
> ? shouldn't we request a removal of "ardour3" *now*?

Yes, let's do it, A3 is dead. We might want to figure something out for
jessie users, but that's for later. (backporting if we have the
manpower)


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

[Debian/GNU]

On 2015-09-20 11:25, Jaromír Mikeš wrote:
>>> i simply see no reason to keep ardour3 around, and it has a crasher bug
>>> (#778363) triggered by loading any MIDI file (i think that should be
>>> raised to "important").
>>
>> I would remove it.

i'd like to hear adrian on this first.

> 
> What should we do with these bugs?
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=ardour
> 
> They are not appropriate probably anymore as we moved ardour4 to ardour 
> package.
> Should we just close them?

once we have confirmation that these bugs are really fixed in the new
version, we can close them.

for this we would need to be able to reproduce the original problem and
then be able to not reproduce it with the newer version.

i at least cannot reproduce #692201 (but haven't tried with an older
version or ardour to actually do reproduce the problem).
i would like to hear from the op before closing this.

i haven't tried repdroducing either #598849 nor #581196.

as for #581196, the op states that the bug really was a user error an
the ticket might be closed, but as i don't fully understand the problem
space and/or the resolution, i would rather not close it now.


as for #598849, the upstream ticket doesn't show any resolution (or - to
be precise - reaction).


dfasr
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

Re: Packaging ardour 4.0

[Jaromír Mikeš]

2015-09-16 12:38 GMT+02:00 Jaromír Mikeš :
> 2015-09-16 11:32 GMT+02:00 IOhannes m zmölnig (Debian/GNU)
> :
>> On 2015-04-19 14:13, Adrian Knoth wrote:
>>>
>>> So here's the suggestion. Instead of
>>>
>>>ardour  -> a2
>>>ardour3 -> a3
>>>ardour4 -> a4
>>>
>>> I propose
>>>
>>>ardour  -> a4
>>>ardour3 -> a3 (legacy tree for jessie)
>>>drop ardour3 after jessie+1 (what's the new codename? ;) )
>>>
>>
>> now that both ardour (4.2) and ardour3 (back to 3.5.403) are uploaded to
>> unstable, i wonder about that last line:
>> shouldn't we drop ardour3 asap? right now?
>>
>> probably adding another transitional package (for stretch).
>>
>> i simply see no reason to keep ardour3 around, and it has a crasher bug
>> (#778363) triggered by loading any MIDI file (i think that should be
>> raised to "important").
>
> I would remove it.

What should we do with these bugs?
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=ardour

They are not appropriate probably anymore as we moved ardour4 to ardour package.
Should we just close them?

best

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

[Debian/GNU]

On 2015-04-19 14:13, Adrian Knoth wrote:
> 
> So here's the suggestion. Instead of
> 
>ardour  -> a2
>ardour3 -> a3
>ardour4 -> a4
> 
> I propose
> 
>ardour  -> a4
>ardour3 -> a3 (legacy tree for jessie)
>drop ardour3 after jessie+1 (what's the new codename? ;) )
> 

now that both ardour (4.2) and ardour3 (back to 3.5.403) are uploaded to
unstable, i wonder about that last line:
shouldn't we drop ardour3 asap? right now?

probably adding another transitional package (for stretch).

i simply see no reason to keep ardour3 around, and it has a crasher bug
(#778363) triggered by loading any MIDI file (i think that should be
raised to "important").


ghmsdf
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

Re: Packaging ardour 4.0

[Jaromír Mikeš]

2015-09-16 11:32 GMT+02:00 IOhannes m zmölnig (Debian/GNU)
:
> On 2015-04-19 14:13, Adrian Knoth wrote:
>>
>> So here's the suggestion. Instead of
>>
>>ardour  -> a2
>>ardour3 -> a3
>>ardour4 -> a4
>>
>> I propose
>>
>>ardour  -> a4
>>ardour3 -> a3 (legacy tree for jessie)
>>drop ardour3 after jessie+1 (what's the new codename? ;) )
>>
>
> now that both ardour (4.2) and ardour3 (back to 3.5.403) are uploaded to
> unstable, i wonder about that last line:
> shouldn't we drop ardour3 asap? right now?
>
> probably adding another transitional package (for stretch).
>
> i simply see no reason to keep ardour3 around, and it has a crasher bug
> (#778363) triggered by loading any MIDI file (i think that should be
> raised to "important").

I would remove it.

best

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

[Jaromír Mikeš]

2015-05-04 23:56 GMT+02:00 Adrian Knoth a...@drcomp.erfurt.thur.de:

 On 4 May 2015 17:04:28 GMT-04:00, Jaromír Mikeš mira.mi...@gmail.com
 wrote:

  Hi Adrian,

 Hi!

 are you still working on different method of repacking?
 If you are fine with current repacking I would go forward and upload.
 Let me know pls.

 Not working on it for the foreseeable future. Whatever we have is good
 enough, so feel free to upload.


Uploaded.

there are still some things to think about.

X: ardour3: shlib-calls-exit usr/lib/ardour4/libardour.so.3.0.0
X: ardour3: shlib-calls-exit usr/lib/ardour4/libgtkmm2ext.so.0.8.3
X: ardour3: shlib-calls-exit usr/lib/ardour4/libpbd.so.4.1.0

Adrian you are involved in upstream development ... is that right?
Can you comment on possible fixes?

W: ardour3: postinst-has-useless-call-to-ldconfig
W: ardour3: postrm-has-useless-call-to-ldconfig

Jonas are these warning connected to this cdbs bug?

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=204975

best 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

[Jonas Smedegaard]

Quoting Jaromír Mikeš (2015-05-05 09:43:59)
 W: ardour3: postinst-has-useless-call-to-ldconfig
 W: ardour3: postrm-has-useless-call-to-ldconfig

 Jonas are these warning connected to this cdbs bug?

 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=204975

I don't know.  Maybe.


 - 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

[Adrian Knoth]

On 4 May 2015 17:04:28 GMT-04:00, Jaromír Mikeš mira.mi...@gmail.com wrote:

 Hi Adrian,


Hi!


are you still working on different method of repacking?
If you are fine with current repacking I would go forward and upload.
Let me know pls.

Not working on it for the foreseeable future. Whatever we have is good enough, 
so feel free to upload.

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

[Jaromír Mikeš]

2015-04-23 15:07 GMT+02:00 Jaromír Mikeš mira.mi...@gmail.com:



 2015-04-23 10:47 GMT+02:00 Adrian Knoth a...@drcomp.erfurt.thur.de:


  http://git.ardour.org/ardour/ardour.git master

 For get-orig-source method (I want to use for repacking) is needed
 working watch file first.
 Is there any web interface to upstream git to we can monitor it with
 uscan?


 Yes, use https://github.com/Ardour/ardour

 Thanks for taking care of this.


 $ debian/rules get-orig-source

 This will give you repacked tarball dfsg1 now.
 Please test it ... if fine upload repacked orig to our repo.
 Sorry I would do it myself but busy at the moment :(


 Hi Adrian,

are you still working on different method of repacking?
If you are fine with current repacking I would go forward and upload.
Let me know pls.

best 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

[Jaromír Mikeš]

2015-04-23 10:47 GMT+02:00 Adrian Knoth a...@drcomp.erfurt.thur.de:


  http://git.ardour.org/ardour/ardour.git master

 For get-orig-source method (I want to use for repacking) is needed
 working watch file first.
 Is there any web interface to upstream git to we can monitor it with
 uscan?


 Yes, use https://github.com/Ardour/ardour

 Thanks for taking care of this.


Hi Adrian,

$ debian/rules get-orig-source

This will give you repacked tarball dfsg1 now.
Please test it ... if fine upload repacked orig to our repo.
Sorry I would do it myself but busy at the moment :(

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

[Adrian Knoth]

http://git.ardour.org/ardour/ardour.git master

For get-orig-source method (I want to use for repacking) is needed
working watch file first.
Is there any web interface to upstream git to we can monitor it with
uscan?


Yes, use https://github.com/Ardour/ardour

Thanks for taking care of this.


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

[Adrian Knoth]

I can have a look on on repacking ... can you send me a link for
upstream git?
We should also add debian/watch file


   git://git.ardour.org/ardour/ardour.git master

Thanks for taking a look!


Copyright file finished


Awesome. Feel free to upload anytime you think it's ready.


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

[Jaromír Mikeš]

2015-04-21 0:11 GMT+02:00 Jaromír Mikeš mira.mi...@gmail.com:



 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:

 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 can have a look on on repacking ... can you send me a link for upstream
git?
We should also add debian/watch file


 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 ;)


Copyright file finished

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

[Jaromír Mikeš]

2015-04-22 16:37 GMT+02:00 Adrian Knoth a...@drcomp.erfurt.thur.de:


  I can have a look on on repacking ... can you send me a link for
 upstream git?
 We should also add debian/watch file


git://git.ardour.org/ardour/ardour.git master


For get-orig-source method (I want to use for repacking) is needed working
watch file first.
Is there any web interface to upstream git to we can monitor it with uscan?

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

[Adrian Knoth]

On 04/21/15 06:53, Jaromír Mikeš wrote:


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?


Yes, works for me, even inside VMs and chroots.


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

[Jaromír Mikeš]

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

Re: Packaging ardour 4.0

[Jaromír Mikeš]

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

Re: Packaging ardour 4.0

[Jaromír Mikeš]

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

[Adrian Knoth]

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

[Jaromír Mikeš]

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

[Jaromír Mikeš]

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

[forum : : für : : umläute]

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

Re: Packaging ardour 4.0

[Jonas Smedegaard]

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

[Adrian Knoth]

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

[Fabian Greffrath]

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

[Jaromír Mikeš]

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

[Jaromír Mikeš]

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

[Fabian Greffrath]

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

[Adrian Knoth]

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

[Felipe Sateler]

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

[Fabian Greffrath]

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

[Fabian Greffrath]

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

Re: Packaging ardour 4.0

[Adrian Knoth]

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

[Jonas Smedegaard]

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

[Felipe Sateler]

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

[Jonas Smedegaard]

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

Re: Packaging ardour 4.0

[Sebastian Ramacher]

Hi Adrian

On 2015-04-19 14:13:02, Adrian Knoth wrote:
 Just wanted to let you know that I'm mostly done with packaging
 ardour4.0 (released yesterday).
 
 I'm currently building in pbuilder and will report back later.
 
 Note that the package is still called ardour3 with a version set to
 4.0~dfsg-1.
 
 Alternatively, we drop/rename ardour to ardour2 and leave the name
 ardour to the newest major release.
 
 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
 rolling release, and only the newest version makes sense.
 
 Upstream is only rolling forward, never backporting. That said:
 
* make ardour(4) the only version in Debian
 
 What I'm saying here is that we're going to release jessie with a
 version of ardour nobody cares about anymore. And I'm fine with that. We
 can continue providing FTBFS fixes in case they arise, but I'm not going
 to look at any bugreports against a3 containing runtime segfaults or the
 like, because they're probably already fixed in a4.
 
 Ardour seems exactly the kind of software where the classic
 distribution model falls apart, similar to Firefox or Chrome. All we do
 is play catching up with upstream.
 
 So here's the suggestion. Instead of
 
ardour  - a2
ardour3 - a3
ardour4 - a4
 
 I propose
 
ardour  - a4
ardour3 - a3 (legacy tree for jessie)
drop ardour3 after jessie+1 (what's the new codename? ;) )

Is there a reason to keep old ardour versions around?

Cheers
-- 
Sebastian Ramacher


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

Re: Packaging ardour 4.0

[Adrian Knoth]

On 04/19/15 14:43, Sebastian Ramacher wrote:

 Hi Adrian

Hi!

 I propose

ardour  - a4
ardour3 - a3 (legacy tree for jessie)
drop ardour3 after jessie+1 (what's the new codename? ;) )
 
 Is there a reason to keep old ardour versions around?

I've asked upstream about this. A4 can open A3 and A2 sessions, so we're
good to drop at least A2.

We initially started with a separate ardour3 package when a3 was still
in its early stages, so this is how we ended up with two different
packages.

Upstream later changed its development model to continuous releases
(instead of a dedicated development branch - same as the Linux kernel
when they gave up on unstable branches).

With A4 being backwards compatible, I'm even more in favour of re-using
the ardour package name for the purpose of a4.


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