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
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.
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 upstrea
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 Develope
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 us
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
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
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)?
--
Alessio Treglia | www.alessiotreglia.com
Debian Developer | ales...@debian.org
Ubuntu Core Developer | quad
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
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
--
A
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 (jeremysa
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
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"
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 rev
On 11-06-18 at 06:08am, Jeremy Salwen wrote:
> 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 ups
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
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 packag
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,
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.co
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
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 Develo
On 11-06-15 at 07:23pm, Jeremy Salwen wrote:
> 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
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
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 as
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
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 so
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 tho
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
28 matches
Mail list logo
