Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "lablie"
* Package name: lablie
Version : 0.6.1-1
* URL : https://gitlab.com/kravemir/lablie
* License : Apache-2.0
* Vcs :
On Fri, Sep 06, 2019 at 01:37:17AM +0900, Yukiharu YABUKI wrote:
> The orig.tar.gz which has different size and contents will be
> REJECTED.
>
> I'd like to upload and accept the package.
So a typical XY problem.
Just changing the top-level directory name is not enough to recreate the
identical
Hi
The orig.tar.gz which has different size and contents will be
REJECTED.
I'd like to upload and accept the package.
original tar.gz
$ LANG=C;ls -la vim-voom_5.3.orig.tar.gz
-rw-r--r-- 1 yabuki yabuki 115841 Aug 14 2018 vim-voom_5.3.orig.tar.gz
gbp buildpackage made:
-rw-r--r-- 1
On Thu, Sep 05, 2019 at 11:29:04PM +0900, Yukiharu YABUKI wrote:
> Hello, there.
>
> I am trying to solve the below problem. I use git buildpackage with
> cowbuilder. How can I chage top directory name of orig.tar.gz which
> made by gbp buildpackage.
>
> I would like change top diretory name to
Hello, there.
I am trying to solve the below problem. I use git buildpackage with
cowbuilder. How can I chage top directory name of orig.tar.gz which
made by gbp buildpackage.
I would like change top diretory name to VOoM-5.3 from vim-voom_5.3.
original:
> tar ztvf vim-voom_5.3.orig.tar.gz
>
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "ascii"
* Package name : ascii
Version : 3.18-2
Upstream Author : [fill in name and email of upstream]
* URL : http://www.catb.org/~esr/ascii/
* License : [fill in]
* Vcs :
On Thu, Sep 05, 15:57, Andrey Rahmatullin wrote
> On Thu, Sep 05, 2019 at 12:47:43PM +0200, Andre Noll wrote:
> > > > There have been no changes since June, so your existing repo should
> > > > still be uptodate.
> > >
> > > You will need to upload a new version, though; the system will not
> > >
On Thu, Sep 05, 2019 at 12:47:43PM +0200, Andre Noll wrote:
> > > There have been no changes since June, so your existing repo should
> > > still be uptodate.
> >
> > You will need to upload a new version, though; the system will not
> > accept a package with the same version number.
>
> I've
On Thu, Sep 05, 10:57, Julian Gilbey wrote
> > There have been no changes since June, so your existing repo should
> > still be uptodate.
>
> You will need to upload a new version, though; the system will not
> accept a package with the same version number.
I've released and tagged v1.0.1.
On Thu, Sep 05, 2019 at 10:10:00AM +0200, Andre Noll wrote:
> Hi Adam,
>
> looks like tfortune needs a new source-only upload to migrate to
> testing. Could you please do this for me? Here's the commands to
> build the source package:
>
> git archive --prefix tfortune-1.0.0/ origin/master
Hi Adam,
looks like tfortune needs a new source-only upload to migrate to
testing. Could you please do this for me? Here's the commands to
build the source package:
git archive --prefix tfortune-1.0.0/ origin/master >
../tfortune_1.0.0.orig.tar.xz
dpkg-buildpackage -S
There
11 matches
Mail list logo
