On Wed, Aug 15, 2018 at 10:09:54AM -0300, eamanu15 wrote:
> Dear Mentors,
>
> Yesterday, I uploaded a package that I ITA. [1] [2]
>
> Something strange happened. The uploaders field on mentors.d.net say a
> different name than I put on d/control.
It is taken from the first existing mentors upload
Dear Mentors,
Yesterday, I uploaded a package that I ITA. [1] [2]
Something strange happened. The uploaders field on mentors.d.net say a
different name than I put on d/control.
Exist a real problem? or that has a reason?
PS: I have some problem with Lintian. I am working in it
[1]
https://ment
gt;
> > And in the https://tracker.debian.org/pkg/cligh not appear my changes.
> >
> > What is happening? What's wrong?
> You cannot upload packages directly to Debian, you need a sponsor. Please
> look at https://mentors.debian.net/intro-maintainers as an introduction
> (especially at the stepas 4 and 5).
>
Thanks! I will read the link!
> --
> WBR, wRAR
>
--
Arias Emmanuel
http://eamanu.com
ter via
> Filezilla, I just see the *.tar.gz and not all the tarball generated with
> dpkg-builpackage.
>
> And in the https://tracker.debian.org/pkg/cligh not appear my changes.
>
> What is happening? What's wrong?
You cannot upload packages directly to Debian, you need
Hello everybody,
I am a new maintainer. I find an interest (for me) package: cligh (
https://tracker.debian.org/pkg/cligh).
This package was in RFA status and I try to adopted it, so I send my ITA
request. This is the #851186 on bugs.debian.org.
So, I downloaded the package, I used the dsc to un
>
>
>
> Wait half an hour and retry: works.
>
umm i try this.. and nothinh,.. but i'll try this again with my key
uploaded in a public server .. maybe replication its slowly
> Conclusion (in my case): it can take some time before
> a freshly uploaded key is taken into account.
>
my ley are into a
Hi,
Date: Fri, 8 Jun 2012 11:42:12 -0430
> i try to upload my dsc packages and sources but i get key singin errors, i
> generated the 4096 key and put in debian mentors profile.. but when i upload
> this happened:
>
> GnuPG signature check failed on XX.changes
> gpg: Signature mad
sorry.. i dont see the header..
i'm using the same key..
i have loade in mentors a id Current GPG key: 4096R/251CEB87
RSA of 4096 bits, ID 251CEB87, created at 2012-05-31
in my machine:
gpg --list-keys
pub 4096R/251CEB87 2012-05-31
uid PICCORO Lenz McKAY (venenux & debian pa
On Fri, Jun 08, 2012 at 11:42:12AM -0430, PICCORO McKAY Lenz wrote:
> i try to upload my dsc packages and sources but i get key singin errors, i
> generated the 4096 key and put in debian mentors profile.. but when i
> upload this happened:
>
> GnuPG signature check failed on XX.change
i try to upload my dsc packages and sources but i get key singin errors, i
generated the 4096 key and put in debian mentors profile.. but when i
upload this happened:
GnuPG signature check failed on XX.changes
gpg: Signature made Fri May 18 23:24:18 2012 UTC using DSA key ID YYY
gp
Il giorno Sat, 17 Jul 2010 23:28:40 +0900
Osamu Aoki ha scritto:
> Is there some trick to indicate previos upload was not the previous
> version in pbuilder or debuild?
-v switch in dpkg-genchanges (which will be pased over to it
by dpkg-buildpackage/debuild).
--
.''`.
: :' : Luca Falavi
Hi,
Osamu Aoki writes:
> I just uploaded xpdf and then realized I was not closing bug for the
> changelog entries from un-uploaaed versions.
>
> I just closed them manually but what did I miss to be like this.
>
> Is there some trick to indicate previos upload was not the previous
> version in p
Osamu Aoki writes:
> Hi,
>
> I just uploaded xpdf and then realized I was not closing bug for the
> changelog entries from un-uploaaed versions.
>
> I just closed them manually but what did I miss to be like this.
>
> Is there some trick to indicate previos upload was not the previous
> version i
On 17/07/2010 16:28, Osamu Aoki wrote:
> Hi,
>
> I just uploaded xpdf and then realized I was not closing bug for the
> changelog entries from un-uploaaed versions.
>
> I just closed them manually but what did I miss to be like this.
>
> Is there some trick to indicate previos upload was not the
Hi,
I just uploaded xpdf and then realized I was not closing bug for the
changelog entries from un-uploaaed versions.
I just closed them manually but what did I miss to be like this.
Is there some trick to indicate previos upload was not the previous
version in pbuilder or debuild?
I know it is
Le Thu, Sep 24, 2009 at 11:49:26PM +0400, Alexander Inyukhin a écrit :
>
> My old GPG key is getting expired soon, so I create a new one
> following instructions described in [1], and I upload it to d.m.n.
> Should I re-upload my package now? Should I increment a version
> number of the package an
Hello!
My old GPG key is getting expired soon, so I create a new one
following instructions described in [1], and I upload it to d.m.n.
Should I re-upload my package now? Should I increment a version
number of the package and post a new RFS?
Thanks.
[1] http://www.debian-administration.org/users
On Wed, Apr 17, 2002 at 05:23:22PM +0200, Piotr Pokora wrote:
> >
> > > I make "Midgard CMS" packages from daily cvs.
> > > We already have sid and woody packages.
> > > Official existing packages do not work
> > > properly , and there is no info from its maintainers
> > > , so how may I uplod m
>
> > I make "Midgard CMS" packages from daily cvs.
> > We already have sid and woody packages.
> > Official existing packages do not work
> > properly , and there is no info from its maintainers
> > , so how may I uplod my packages?
>
> I would start by contacting the current Debian maintainer
On Wed, 17 Apr 2002, pp wrote:
> I make "Midgard CMS" packages from daily cvs.
> We already have sid and woody packages.
> Official existing packages do not work
> properly , and there is no info from its maintainers
> , so how may I uplod my packages?
I would start by contacting the current De
On Wed, Apr 17, 2002 at 05:23:22PM +0200, Piotr Pokora wrote:
> >
> > > I make "Midgard CMS" packages from daily cvs.
> > > We already have sid and woody packages.
> > > Official existing packages do not work
> > > properly , and there is no info from its maintainers
> > > , so how may I uplod
Hello all!
I make "Midgard CMS" packages from daily cvs.
We already have sid and woody packages.
Official existing packages do not work
properly , and there is no info from its maintainers
, so how may I uplod my packages?
And change official ones?
Piotras
--
To UNSUBSCRIBE, email to [EMA
22 matches
Mail list logo
