Re: Bug#654347: Remove SLV2 dependency in favor of Lilv
Hi Alessio, I'm finally out of school for the summer, so I'll probably do this soon. The actual work is very small. Jeremy On Wed, May 16, 2012 at 4:32 PM, Alessio Treglia wrote: > Hi Jeremy, > > On Tue, Jan 3, 2012 at 8:33 AM, Alessio Treglia > wrote: > > Package: lv2file > > Version: 0.82-1 > > Severity: important > > > > Hi! > > > > SLV2 has been deprecated in favor of Lilv and we intend to remove it > soon: > > Any news on this? > > -- > Alessio Treglia | www.alessiotreglia.com > Debian Developer | ales...@debian.org > Ubuntu Core Developer| quadris...@ubuntu.com > 0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A > ___ 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#654347: Remove SLV2 dependency in favor of Lilv
Hi Alessio, I have released a new version and updated the debian packaging in the alioth git. Jeremy On Thu, May 17, 2012 at 2:10 AM, Jeremy Salwen wrote: > Hi Alessio, > > I'm finally out of school for the summer, so I'll probably do this soon. > The actual work is very small. > > Jeremy > > > On Wed, May 16, 2012 at 4:32 PM, Alessio Treglia wrote: > >> Hi Jeremy, >> >> On Tue, Jan 3, 2012 at 8:33 AM, Alessio Treglia >> wrote: >> > Package: lv2file >> > Version: 0.82-1 >> > Severity: important >> > >> > Hi! >> > >> > SLV2 has been deprecated in favor of Lilv and we intend to remove it >> soon: >> >> Any news on this? >> >> -- >> Alessio Treglia | www.alessiotreglia.com >> Debian Developer | ales...@debian.org >> Ubuntu Core Developer| quadris...@ubuntu.com >> 0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A >> > > ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Request for Sponsorship of real-time music analysis program Tartini
Hi, I'm looking for a sponsor for a real-time music analysis program Tartini. It provides highly accurate pitch, loudness, timbre and vibrato analysis. The software website is http://miracle.otago.ac.nz/tartini/. The RFP bug is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515003. I have already created proper packaging, which is available at https://github.com/jeremysalwen/tartini-debian. I have been maintaining two packages under Debian Multimedia Maintainers, lv2file, and so-synth-lv2 for a couple of years now. Thanks, Jeremy Salwen ___ 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#622179: yoshimi: Segmentation fault when starting.
Package: yoshimi Version: 0.060.8-1 Severity: grave Justification: renders package unusable When starting up yoshimi, it segmentation faults. This does not occur in the 0.058 version. I don't have debug symbols, but I got the following backtrace Program received signal SIGSEGV, Segmentation fault. 0x in ?? () (gdb) backtrace #0 0x in ?? () #1 0x004b8c91 in JackEngine::openAudio() () #2 0x004be57d in JackClient::openAudio() () #3 0x0050b40e in main () -- System Information: Debian Release: wheezy/sid APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.37-2-amd64 (SMP w/6 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages yoshimi depends on: ii jackd 5JACK Audio Connection Kit (default ii libasound2 1.0.23-2.1 shared library for ALSA applicatio ii libc6 2.11.2-13Embedded GNU C Library: Shared lib ii libfftw3-3 3.2.2-1 library for computing Fast Fourier ii libfltk1.1 1.1.10-4 Fast Light Toolkit - shared librar ii libgcc1 1:4.6.0-2GCC support library ii libjack-jackd2-0 [libja 1.9.6~dfsg.1-2 JACK Audio Connection Kit (librari ii libmxml12.6-2small XML parsing library (runtime ii libstdc++6 4.5.2-6 The GNU Standard C++ Library v3 ii yoshimi-data0.060.8-1Presets for Yoshimi ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime yoshimi recommends no packages. yoshimi suggests no packages. -- no debconf information ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Bug#622179: is unreproducible
Uninstalling and reinstalling yoshimi several times did not work (Trying different versions). However compiling from source and then installing did (.060, and then .062, from apt-get source and tarballs). After compiling from source and installing, then uninstalling and installing from the repositories, it works for me now. So you can close this bug if you like. Jeremy On Mon, Apr 11, 2011 at 2:11 PM, Alessio Treglia wrote: > See the attached screenshot, I'll provide a -DBG package soon. > > Regards, > > -- > Alessio Treglia | www.alessiotreglia.com > Debian Developer | ales...@debian.org > Ubuntu Core Developer| quadris...@ubuntu.com > 0FEC 59A5 E18E E04F 6D40 593B 45D4 8C7C DCFC 3FD0 > ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Bug#622179: yoshimi: Segmentation fault when starting.
I can't reproduce the segmentation fault any more. Jeremy On Wed, Jun 1, 2011 at 6:49 AM, Alessio Treglia wrote: > tags 622179 moreinfo > thanks > > Hi Jeremy, > > could you try to reproduce this with the latest upstream release > available in Debian sid? > > -- > Alessio Treglia | www.alessiotreglia.com > Debian Developer | ales...@debian.org > Ubuntu Core Developer| quadris...@ubuntu.com > 0FEC 59A5 E18E E04F 6D40 593B 45D4 8C7C DCFC 3FD0 > ___ 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: Invitation to join the Debian Multimedia Maintainers team
Hi Jonas, I'm confused, because there seem to be two standards by which one might join the Debian Multimedia Maintainers team. The first seems to be an informal one, by which someone who has created a couple of debian packages is invited to join (Alessio extended to me a similar offer). If I thought this were the final word, I would be happy to join. However, when I go to the website to look into joining, I find a second set of standards, including the items: - are familiar with managing bugs in debian. - agree to review other's work (patches and packages). Neither of which I am okay with. I am not familiar with managing bugs in debian. I simply don't know how to do anything besides send an email to the bug report. As for the second point, I suppose I could technically review others' work, but it probably wouldn't be much of a review. Much of this stuff is over my head. If I were to look at the source of Ardour, for instance, it would probably take me a week to make heads or tails of it. Jeremy On Thu, Jun 2, 2011 at 6:48 AM, Jonas Smedegaard wrote: > Hi Jeremy, > > I notice the Debian package so-synth-lv2 emerged in Debian unstable > today. > > Cool! > > Would you perhaps be interested in maintaining that package under the > umbrella of the Debian Multimedia Maintainers? We would love more > multimedia enthusiasts involved :-) > > More info here: http://wiki.debian.org/DebianMultimedia > > > This email also sent to our team mailinglist, and I recommend you reply > there (Reply-To set accordingly). > > > Kind regards, > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private > ___ 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: Invitation to join the Debian Multimedia Maintainers team
Hi, [long response time too] A couple things: 1. I should probably clarify that I certainly can *handle* bugs filed against any of my packages, in the sense that I can respond to them, fix them, and create a new package with the new version, but I basically had no experience tagging or assigning or triaging or whatever other things you can do with the metadata. 2. While I'm totally down with teamwork, I've been subscribed to the pkg-multimedia-maintainer mailing list for a while now, and I have to say that the volume is almost too much for me to handle on a daily basis, and certainly will be in a couple months when I start school again (not to mention the -commits mailing list, which seems to be even *higher* volume). So honestly, although you've convinced me that I'd be qualified to join the team, and I'll hang out with you guys and help out when I have time, I just don't think I could handle being subscribed to the mailing lists for any substantial amount of time. Jeremy On Mon, Jun 6, 2011 at 3:21 AM, Jonas Smedegaard wrote: > Hi Jeremy (and fellow Multimedia Maintainers), > > [sorry forthe lateresponse!] > > On 11-06-02 at 07:50am, Jeremy Salwen wrote: > > I'm confused, because there seem to be two standards by which one > > might join the Debian Multimedia Maintainers team. The first seems to > > be an informal one, by which someone who has created a couple of > > debian packages is invited to join (Alessio extended to me a similar > > offer). If I thought this were the final word, I would be happy to > > join. However, when I go to the website to look into joining, I find > > a second set of standards, including the items: > > > >- are familiar with managing bugs in debian. > >- agree to review other's work (patches and packages). > > > > Neither of which I am okay with. I am not familiar with managing bugs > > in debian. I simply don't know how to do anything besides send an > > email to the bug report. > > > > As for the second point, I suppose I could technically review others' > > work, but it probably wouldn't be much of a review. Much of this > > stuff is over my head. If I were to look at the source of Ardour, for > > instance, it would probably take me a week to make heads or tails of > > it. > > The requirement about managing bugs is mostly aimed at contributors > *less* involved than you - in fact I am surprised by your comment: As > maintainer for a package officially part of Debian, you *must* be able > to handle bugs filed against it! > > > That other requirement about reviewing works of others really is about > interest in doing teamwork. Feel free to ask questions, but don't join > if you do not intend to contribute yourself. That's more fun for us all. > > > But both those requirements are about _interest_ in such work. We are > not an sxclusive club and we do not require university degrees or DD > membership for you to work with us. > > Have a look at our mailinglist, or join our IRC channel. I am confident > that you will find us to be pretty nice people to hang out with :-D > > > Kind regards, > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private > ___ 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: Invitation to join the Debian Multimedia Maintainers team
Okay fine, You've convinced me. I've subscribed to the mailing lists, but directed them to a folder I'll check from time to time. So, 1. I have an alioth account called jeremysalwen-guest 2. I've subscribed to the mailing lists 3. I'm not scared of Debian bugs 4. I'm happy to help anyone when I have the time. A little about myself: My name is Jeremy Salwen, and I like to program audio processing software. When doing audio stuff I mainly write in C, or possibly with a little C++. In particular, I've written a few simple programs and some plugins, but mainly I find myself porting other peoples' software to the LV2 plugin format (which I really like, by the way), As I almost always write software to scratch a particular itch or interest of mine, I like to think that my software would be useful to other people, which is why I started getting involved with packaging my own and other peoples' software for debian. I use git-buildpackage + quilt to make my packages. That's All! Jeremy On Sun, Jun 12, 2011 at 8:56 PM, Jonas Smedegaard wrote: > On 11-06-12 at 07:38pm, Jeremy Salwen wrote: > > 1. I should probably clarify that I certainly can *handle* bugs filed > > against any of my packages, in the sense that I can respond to them, > > fix them, and create a new package with the new version, but I > > basically had no experience tagging or assigning or triaging or > > whatever other things you can do with the metadata. > > Sounds great! > > I feel you (and me too) should not read that too literally. Point is > not that you must be super clever juggling bugreports to work in this > team, but that you acknowledge that it involved juggling bugreports and > you do not feel uncomfortably with that. > > Perhaps we should rephrase that sentence, to not scare off other > potential future team members. What do others think? > > > > 2. While I'm totally down with teamwork, I've been subscribed to the > > pkg-multimedia-maintainer mailing list for a while now, and I have to > > say that the volume is almost too much for me to handle on a daily > > basis, and certainly will be in a couple months when I start school > > again (not to mention the -commits mailing list, which seems to be > > even *higher* volume). > > No need for "daily basis" - not at all! > > This is a volunteer project, and there is no requirement in this team > that we commit any specific amount of time on it. Heck, if you wanna > work with us once a year I would still be happy to consider you a team > member! :-D > > > > So honestly, although you've convinced me that I'd be qualified to > > join the team, and I'll hang out with you guys and help out when I > > have time, I just don't think I could handle being subscribed to the > > mailing lists for any substantial amount of time. > > If mailinglist traffic level discourages your joining us, then please do > consider to simply setup your mail handling to reroute list traffic to a > separate folder to not get bogged down by it. Point of you joining the > list is not that you are alert and always "on duty", but that you > acknowledge the _maintainance_ part of the task of maintaining packages. > And again, the actual amount of devotion is fluid - can once a week or > once a month you pop by, or even more infrequently since we are a team > that can cover for each other. :-) > > > So all in all, I still think you should consider joining our team. > > > Regards, > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private > ___ 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: Invitation to join the Debian Multimedia Maintainers team
Yes, certainly. Also, I'd like to maintain the Tartini package under the umbrella. Jeremy On Thu, Jun 16, 2011 at 7:12 AM, Alessio Treglia wrote: > On Wed, Jun 15, 2011 at 11:23 PM, Jeremy Salwen > wrote: > > Okay fine, You've convinced me. > > And I'm happy to see you join the team: welcome aboard!! > > So would you now move lv2file,so-synth-lv2's packaging under the > team's umbrella? > > -- > Alessio Treglia | www.alessiotreglia.com > Debian Developer | ales...@debian.org > Ubuntu Core Developer| quadris...@ubuntu.com > 0FEC 59A5 E18E E04F 6D40 593B 45D4 8C7C DCFC 3FD0 > ___ 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: Invitation to join the Debian Multimedia Maintainers team
I actually already have git repositories for both these packages on github. It would be nice if they were synchronized: https://github.com/jeremysalwen/So-synth-LV2 https://github.com/jeremysalwen/lv2file On Fri, Jun 17, 2011 at 5:44 AM, Alessio Treglia wrote: > On Thu, Jun 16, 2011 at 8:34 PM, Jeremy Salwen > wrote: > > Yes, certainly. Also, I'd like to maintain the Tartini package under the > > umbrella. > > Great! > If you agree, I'd import the current packaging of lv2file and > so-synth-lv2 into our git area. > > > -- > Alessio Treglia | www.alessiotreglia.com > Debian Developer | ales...@debian.org > Ubuntu Core Developer| quadris...@ubuntu.com > 0FEC 59A5 E18E E04F 6D40 593B 45D4 8C7C DCFC 3FD0 > ___ 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: Invitation to join the Debian Multimedia Maintainers team
A little confused. I do upstream development and debian packagin in the same git repository. I have the upstream branch which I work on and occasionally tag, and I have the master branch, in which I keep the debian packaging and merge in upstream versions. I then update the changelog and tag the commit. I thought this was supposed to be the layout of debian packages in git. If you're asking me to remove the debian directories from the upstream branch, no need, there is no debian directory in the upstream branch. If you're asking me to remove the debian branch, that makes more sense, but I don't quite get why. I need somewhere to backup my packaging work, and I don't think I have write access to the git repositories you set up. Also, I'm not sure if: 1. upstream work is allowed in the pkg-multimedia repository 2. intermediate packaging work is allowed in the pkg-multimedia repository 3. it would be okay to have the github and pkg-multimedia repositories sync up. (or at least share commits). 4. Am I supposed to have write access to these repositories, or is that reserved for DDs? Thanks Jeremy On Sat, Jun 18, 2011 at 4:21 AM, Alessio Treglia wrote: > On Fri, Jun 17, 2011 at 9:51 PM, Jeremy Salwen > wrote: > > I actually already have git repositories for both these packages on > github. > > It would be nice if they were synchronized: > > https://github.com/jeremysalwen/So-synth-LV2 > > https://github.com/jeremysalwen/lv2file > > I'm about to import the packaging of lv2file and so-synth-lv2 with > git-import-dscs --pristine-tar, so please remove the 'debian' > directories from upstream sources trees as they are unnecessary now. > > http://anonscm.debian.org/gitweb/?p=pkg-multimedia/lv2file.git > http://anonscm.debian.org/gitweb/?p=pkg-multimedia/so-synth-lv2.git > > > -- > Alessio Treglia | www.alessiotreglia.com > Debian Developer | ales...@debian.org > Ubuntu Core Developer| quadris...@ubuntu.com > 0FEC 59A5 E18E E04F 6D40 593B 45D4 8C7C DCFC 3FD0 > ___ 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: Invitation to join the Debian Multimedia Maintainers team
Hi Jonas and Alessio,
I was concerned about the extra commits in the git repository firing off
messages, but I realize it's probably only certain branches triggering this.
Alessio, in the workflow you described, the upstream.trunk branch is what I
was referring to as "intermediate packaging work"
I have an account on alioth (jeremysalwen-guest) and I requested to join the
team a little while ago, but I haven't been accepted yet.
as for
> I have asked you to remove the debian directory at least from the release
tarballs just to save some KiBs.
I wasn't aware the dir was included. I'll try to fix that in the future.
I'll try to set up the git repositories properly once I have a change.
There's this project I'm working on that I'm really pushing to finish right
now, so I'll probably be inactive for a few more days.
Jeremy
On Mon, Jun 20, 2011 at 11:50 AM, Alessio Treglia wrote:
> Hi Jeremy,
>
> sorry for the long delay.
>
> On Sat, Jun 18, 2011 at 10:08 AM, Jeremy Salwen
> wrote:
> > A little confused. I do upstream development and debian packagin in the
> > same git repository.
>
> And this isn't bad, you can develop your software the way you prefer,
> however the packaging should be reviewed through our git repository.
>
> > If you're asking me to remove the debian directories from the upstream
> > branch, no need, there is no debian directory in the upstream branch.
>
> I have asked you to remove the debian directory at least from the
> release tarballs just to save some KiBs.
>
> > 1. upstream work is allowed in the pkg-multimedia repository
>
> There wouldn't be any particular problem for me. A good workflow may be:
>
> 1. Work on upstream side by committing the changes into a new
> upstream.trunk branch.
> 2. Once the sources are ready to be released:
> a. Merge "upstream.trunk" into "upstream" and tag the latter
> properly ("upstream/%(version)s").
> b. Prepare an orig.tar.gz, commit it into the pristine-tar branch
> c. Merge upstream into master.
>
> > 2. intermediate packaging work is allowed in the pkg-multimedia
> repository
>
> I fail to catch the point: what does "intermediate packaging work" mean?
>
> > 3. it would be okay to have the github and pkg-multimedia repositories
> sync
> > up. (or at least share commits).
>
> There would no need to set up such a sync if you follow that workflow
> I drafted above.
>
> > 4. Am I supposed to have write access to these repositories, or is that
> > reserved for DDs?
>
> You'd just need to have an account on Alioth and join the team.
>
> Cheers,
>
> --
> Alessio Treglia | www.alessiotreglia.com
> Debian Developer | ales...@debian.org
> Ubuntu Core Developer| quadris...@ubuntu.com
> 0FEC 59A5 E18E E04F 6D40 593B 45D4 8C7C DCFC 3FD0
>
___
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: Invitation to join the Debian Multimedia Maintainers team
On Wed, Jun 22, 2011 at 5:50 AM, Alessio Treglia wrote: > On Tue, Jun 21, 2011 at 10:36 AM, Jeremy Salwen > wrote: > > Alessio, in the workflow you described, the upstream.trunk branch is what > I > > was referring to as "intermediate packaging work" > > > > I have an account on alioth (jeremysalwen-guest) and I requested to join > the > > team a little while ago, but I haven't been accepted yet. > > I've added you, so... welcome aboard! :) > > I've already set up both lv2file and so-synth-lv2 repos: >http://anonscm.debian.org/gitweb/?p=pkg-multimedia/lv2file.git > http://anonscm.debian.org/gitweb/?p=pkg-multimedia/so-synth-lv2.git > > Your "upstream" branches on github have been merged into the > respective UPSTREAM.trunk branches. > To retrieve the code and set up your local copy: > > gbp-clone git+ssh://git.debian.org/git/pkg-multimedia/$PACKAGE.git > cd $PACKAGE && git fetch origin UPSTREAM.trunk:UPSTREAM.trunk > > So now you are able to work as upstream by directly committing your > changes to the UPSTREAM.trunk branches. > When you feel comfortable with a certain state of things, please keep > in mind what follows: > > * Use the capitalized form "UPSTREAM/%(version)s" to mark commits > in your "trunk" branches in order to avoid conflicts with the > "upstream/%(version)s" used when importing the new release into > the upstream branches. > * After tagging a new release, please create a tarball and follow the > procedure described in our wiki: > > git-import-orig --pristine-tar ../$(PACKAGE)_$(RELEASE).orig.tar.gz > > Please don't forget the --pristine-tar option (which is set by default > in the debian/gbp.conf config file, though), it is needed to avoid > downloading stuff from the Debian archive at build time. > For any question or if you don't like this way, let me know! > > Cheers, > > -- > Alessio Treglia | www.alessiotreglia.com > Debian Developer | ales...@debian.org > Ubuntu Core Developer| quadris...@ubuntu.com > 0FEC 59A5 E18E E04F 6D40 593B 45D4 8C7C DCFC 3FD0 > Hi Alessio, How would I get access to the git.debian.org server? Right now I get public key denied errors if I try to ssh in or do a non-anonymous clone. Jeremy ___ 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: Matteo F. Vescovi joined Debian Multimedia Maintainers team
Welcome Matteo! On Sat, Aug 6, 2011 at 4:41 AM, Alessio Treglia wrote: > Hi all, > > right few minutes ago, Matteo F. Vescovi joined the Debian Multimedia > Maintainers team on Alioth, willing to work on the packaging of > libmp4v2: please, give him a warm welcome! > > Matteo, have you already checked our policies [1]? > There are some other packages you intend to bring under DMM team's > umbrella? > > [1] > http://wiki.debian.org/DebianMultimedia/DevelopPackaging#Packaging_guidelines > > -- > Alessio Treglia | www.alessiotreglia.com > Debian Developer | ales...@debian.org > Ubuntu Core Developer| quadris...@ubuntu.com > 0FEC 59A5 E18E E04F 6D40 593B 45D4 8C7C DCFC 3FD0 > > ___ > pkg-multimedia-maintainers mailing list > pkg-multimedia-maintainers@lists.alioth.debian.org > > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers > ___ 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: Invitation to join the Debian Multimedia Maintainers team
I just have. Is there anything else I need to do? On Fri, Aug 5, 2011 at 3:17 AM, Alessio Treglia wrote: > On Thu, Aug 4, 2011 at 8:47 PM, Jeremy Salwen > wrote: > > How would I get access to the git.debian.org server? Right now I get > public > > key denied errors if I try to ssh in or do a non-anonymous clone. > > Have you uploaded your SSH key? [1] > > [1] https://alioth.debian.org/account/editsshkeys.php > > -- > Alessio Treglia | www.alessiotreglia.com > Debian Developer | ales...@debian.org > Ubuntu Core Developer| quadris...@ubuntu.com > 0FEC 59A5 E18E E04F 6D40 593B 45D4 8C7C DCFC 3FD0 > ___ 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: Invitation to join the Debian Multimedia Maintainers team
On Tue, Aug 9, 2011 at 9:57 AM, Alessio Treglia wrote: > On Sun, Aug 7, 2011 at 12:11 PM, Jeremy Salwen > wrote: > > I just have. Is there anything else I need to do? > > So, you still fail to login to git.debian.org (via ssh)? > > Yes, and I just verified again that my key is in there and that I still get publickey denied errors when I try to ssh in. Jeremy ___ 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: Invitation to join the Debian Multimedia Maintainers team
I'm logging in as jeremysalwen-guest. On Wed, Aug 10, 2011 at 5:53 AM, Alessio Treglia wrote: > On Tue, Aug 9, 2011 at 9:10 PM, Jeremy Salwen > wrote: > > Yes, and I just verified again that my key is in there and that I still > get > > publickey denied errors when I try to ssh in. > > Which username are you using to log in? > > > -- > Alessio Treglia | www.alessiotreglia.com > Debian Developer | ales...@debian.org > Ubuntu Core Developer| quadris...@ubuntu.com > 0FEC 59A5 E18E E04F 6D40 593B 45D4 8C7C DCFC 3FD0 > ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Tartini
Hi all, I have pushed packaging for Tartini ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515003) to a new repository on alioth. Could someone review that I'm doing it correctly? Thanks, Jeremy ___ 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: Invitation to join the Debian Multimedia Maintainers team
Hi Alessio, I've figured out the alioth SSH issues. Now I have a question about the build process: I have some changes which I merged into UPSTREAM.trunk. Now I want to package them as a new release. Normally I would use git-buildpackage to automatically generate a .orig tarball from my upstream branch. But with this workflow I'm only modifying the upstream branch by doing a git-import-orig, so I need to get a tarball before I run git-buildpackage at all. Is there another way to easily turn a commit on UPSTREAM.trunk into a source tarball ready for import into upstream? Jeremy On Sat, Aug 13, 2011 at 12:40 PM, Alessio Treglia wrote: > On Thu, Aug 11, 2011 at 3:37 AM, Jeremy Salwen > wrote: > > I'm logging in as jeremysalwen-guest. > > I don't know :( > Please have a look at this: >http://wiki.debian.org/Alioth/SSH > > -- > Alessio Treglia | www.alessiotreglia.com > Debian Developer | ales...@debian.org > Ubuntu Core Developer| quadris...@ubuntu.com > 0FEC 59A5 E18E E04F 6D40 593B 45D4 8C7C DCFC 3FD0 > ___ 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: Tartini
On Sat, Dec 24, 2011 at 10:26 PM, Jonas Smedegaard wrote: > On 11-12-24 at 09:31pm, Matteo F. Vescovi wrote: > > On 24/12/2011 18:12, Jonas Smedegaard wrote: > > >Please beware that asking a negated question is impolite: Similar to > > >"when did you stop beating your spouse?" it implies an accusation. > > > > Gosh! Never meant to be so rude. :-( Sorry. > > Uhm, just "impolite" - most folks won't even notice it. I just happen > to be nitpicking with words, and find mechanisms like this interesting. > > > > >>debian/copyright: > > >> you need to re-work it all, to be more DEP-5 compliant [1] > > > > > >DEP-5 is cool, and personally I use it always, but beware that it is > > >optional. > > > > OK. When I started packaging few months ago, guys at debian-mentors > > told me that copyright is very important for Debian and it would have > > been nice providing something well done, maybe in DEP-5. So I thought > > it was the option of choice, even though not mandatory. > > Makes sense. > > ...and if you do use DEP-5 then you should ensure that you follow the > standard. I was just reacting on the phrasing of the response, which > could be misread as DEP-5 formatting of debian/copyright is mandatory. > > > Regards, > > - Jonas > > Okay, I've made all the suggested changes and pushed again. By the way, I was not at all offended by your email, Matteo, although I could imagine someone with a thin skin being bothered by it. Jeremy ___ 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: Invitation to join the Debian Multimedia Maintainers team
Hi Alessio, Thanks, I've figured it all figured out. I've pushed the changes. Jeremy On Mon, Dec 26, 2011 at 6:38 AM, Alessio Treglia wrote: > Hi Jeremy, > > On Sat, Dec 24, 2011 at 11:55 AM, Jeremy Salwen > wrote: > [ ] > > before I run git-buildpackage at all. Is there another way to easily > turn a > > commit on UPSTREAM.trunk into a source tarball ready for import into > > upstream? > > git archive --format=tar --prefix=lv2file-0.82/ UPSTREAM/0.82 | bzip2 > -9 >../lv2file_0.82.orig.tar.bz2 > > Regards, > > -- > Alessio Treglia | www.alessiotreglia.com > Debian Developer | ales...@debian.org > Ubuntu Core Developer| quadris...@ubuntu.com > 0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A > > ___ > pkg-multimedia-maintainers mailing list > pkg-multimedia-maintainers@lists.alioth.debian.org > > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers > ___ 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] lv2file packaging annotated tag, debian/0.82-1, created. debian/0.82-1
Hi Alessio, Sorry about that. I'll make sure not to do so next time. Jeremy On Wed, Dec 28, 2011 at 4:31 AM, Alessio Treglia wrote: > On Tue, Dec 27, 2011 at 11:23 AM, > wrote: > > The annotated tag, debian/0.82-1 has been created > > Jeremy, > > just as small note, the 'debian/*' tags should be added only after the > package has been uploaded. > > Cheers, and thanks for the great work! > > -- > Alessio Treglia | www.alessiotreglia.com > Debian Developer | ales...@debian.org > Ubuntu Core Developer| quadris...@ubuntu.com > 0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A > > ___ > pkg-multimedia-maintainers mailing list > pkg-multimedia-maintainers@lists.alioth.debian.org > > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers > ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
