On Sunday 24 August 2008 21:49:34 Jonathan Wiltshire wrote:
> On Sun, Aug 24, 2008 at 09:37:01PM +0300, George Danchev wrote:
--cut--
> No, that's fine. I'll close it when it goes in (presumably I'll get a
> mail when it does?)
Yes, we will be mailed about that.
> I have another package that's al
On Sun, Aug 24, 2008 at 09:37:01PM +0300, George Danchev wrote:
> option to dpkg-buildpackage giving it the first package version found in the
> changelog (1.0.0-1) in order to include all the entries in the changes file,
> but in fact it appeared to just start from that version on, not including
On Sunday 24 August 2008 21:09:06 Jonathan Wiltshire wrote:
> On Sun, Aug 24, 2008 at 08:49:21PM +0300, George Danchev wrote:
> > Okay, uploaded, thanks for your patience. This will go through Debian NEW
> > queue [1] which will take some time.
>
> Cool, thanks :)
Welcome.
> I've never reached th
On Sun, Aug 24, 2008 at 08:49:21PM +0300, George Danchev wrote:
> Okay, uploaded, thanks for your patience. This will go through Debian NEW
> queue [1] which will take some time.
Cool, thanks :)
>
> I dared to change your last debian/changelog entry (I hope it is ok with you)
> from:
> * Incr
On Sunday 24 August 2008 16:23:55 Jonathan Wiltshire wrote:
Hello,
> > Probably I wasn't clear enough with my previous message, but I now see
> > that I wrote "1.0.0-2 or 1.0.0-1 in your debian/changelog". So, in a
> > package version like A.B.C-X.Y, in the second part (the debian revision)
> >
On Sun, Aug 24, 2008 at 05:16:12AM +0300, George Danchev wrote:
> perform build/lint/fix/install/deinstall/fix cycles at will. Using a clean
> chrooted system also brings the benefit that unsatisfied build depends are
> easily caught, and you are sure that your binaries will not link with any
>
On Sunday 24 August 2008 00:59:00 Jonathan Wiltshire wrote:
> On Sun, Aug 24, 2008 at 12:28:46AM +0300, George Danchev wrote:
> > > > Also, you can use the most recent 3.8.0 standards version, and as I
> > > > can see there are no changes needed to the package, but anyway you
> > > > can check that
On Sat, Aug 23, 2008 at 10:59:00PM +0100, Jonathan Wiltshire wrote:
> Perhaps I have just confused myself, but
> http://www.debian.org/devel/join/nm-checklist says this:
>
> "For the NM process to be the most efficient, Applicants should have
> already contributed significantly to Debian. This can
On Sun, Aug 24, 2008 at 12:28:46AM +0300, George Danchev wrote:
> > > Also, you can use the most recent 3.8.0 standards version, and as I
> > > can see there are no changes needed to the package, but anyway you can
> > > check that with: /usr/share/doc/debian-policy/upgrading-checklist.txt.gz.
> >
On Saturday 23 August 2008 23:08:08 Jonathan Wiltshire wrote:
> On Sat, Aug 23, 2008 at 10:28:47PM +0300, George Danchev wrote:
> > I can't figure out why you want to NMU your own package, perhaps there
> > might be some reason I can't think of right now or it is just an
> > unintentional blund
On Sat, Aug 23, 2008 at 10:28:47PM +0300, George Danchev wrote:
> I can't figure out why you want to NMU your own package, perhaps there
> might
> be some reason I can't think of right now or it is just an unintentional
> blunder.
Could you clarify NMU?
> Also, you can use the most rece
On Saturday 23 August 2008 21:20:15 Jonathan Wiltshire wrote:
> Dear mentors,
>
> I am looking for a sponsor for my package "replaceit", closing ITP
> #490695.
Hello,
I can't figure out why you want to NMU your own package, perhaps there
might
be some reason I can't think of right now or
Dear mentors,
I am looking for a sponsor for my package "replaceit", closing ITP
#490695.
* Package name: replaceit
Version : 1.0.0-1.1
Upstream Author : Paul L Daniels <[EMAIL PROTECTED]>
* URL : http://pldaniels.com/replaceit/
* License : BSD
Section
13 matches
Mail list logo
