Hi Gerrit,
Alright, would it help moving forward if I were doing that? Reverting
to 2014.65 is easy, and the current 2015.68-1 could always be uploaded
once 2014.65-1 has entered testing. It'd be quite sad to upload known
bugs in a package containing multiple lintian warnings and errors [0],
Control: owner -1 !
Control: tag -1 moreinfo
Hi Johan,
* Imported Upstream version 2.3.0 (Closes: #726069)
* Bump standards version (no changes needed)
* Bump library package number
* Update install filename
* Switch to debhelper 9 - enable multiarch
multiarch should be mentioned in
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package libharu
* Package name: libharu
Version : 2.3.0+dfsg-1~exp1
Upstream Author : [fill in name and email of upstream]
* URL : http://libharu.org
* License
Hi,
Done.
[snip]
Done.
The testsuite isn't included in the distribution tar file generated by
upstream. I filed an upstream github but to include the testsuite:
https://github.com/niwinz/django-jinja/issues/135
I don't see the package on mentors...
did you upload it?
cheers,
G.
Gianfranco Costamagna costamagnagianfra...@yahoo.it wrote:
I don't see the package on mentors...
did you upload it?
Sorry, the package is now updated on mentors.
--
Edward.
Gianfranco Costamagna costamagnagianfra...@yahoo.it wrote:
the packaging looks mostly good.
Just a few questions:
python-setuptools (= 0.6b3),
the version is already satisfied in old old stable, you can remove it.
Done.
setup.py
install_requiresjinja2 =2.5,
django =1.4,
they
On Thu, Aug 20, 2015 at 11:19 AM, Gianfranco Costamagna
costamagnagianfra...@yahoo.it wrote:
Looking at the policy I think it is better to document this in
debian/copyright. I like to document why I remove files from the
original source.
but you didn't remove them anymore, right?
anyway, let
On Thu, Aug 20, 2015 at 10:29 AM, Gianfranco Costamagna
costamagnagianfra...@yahoo.it wrote:
Control: owner -1 !
Control: tag -1 moreinfo
Hi Johan,
multiarch should be mentioned in control file.
https://wiki.debian.org/Multiarch/Implementation
Ok, I will check - some time since I last
Gianfranco Costamagna costamagnagianfra...@yahoo.it wrote:
well, it appeared at the end
Copyright: 2015, Edward Betts
please add your mail
Done.
I'm rebuilding right now to see if the Runtime-Dependencies
are correctly picked up :)
if you can fix this in the meanwhile...
I've added my
Your message dated Thu, 20 Aug 2015 09:44:27 + (UTC)
with message-id 167158709.4529457.1440063867783.javamail.ya...@mail.yahoo.com
and subject line Re: Bug#796187: RFS: [ITP] django-jinja/1.4.1-1
has caused the Debian Bug report #796187,
regarding RFS: [ITP] django-jinja/1.4.1-1
to be marked
Hugo,
Sounds good. New package uploaded in the same place
(http://mentors.debian.net/debian/pool/main/g/git-lfs/git-lfs_0.5.4-1.dsc
http://mentors.debian.net/debian/pool/main/g/git-lfs/git-lfs_0.5.4-1.dsc)
with the new copyright file. What are the next steps?
Stephen
On Aug 19, 2015, at
Hi Vincent,
Live from Debconf15.
On 19-08-15 21:29, Vincent Blut wrote:
I am looking for a sponsor for my package chrony
Please note this is a first manual inspection. Not all items are
critical, most are just nitpicks or tips or questions.
Please add the CVE numbers that were fixed by
BuiltSignedUploaded, thanks for your contribution to Debian!
cheers,
G.
Il Giovedì 20 Agosto 2015 11:54, Edward Betts edw...@4angle.com ha scritto:
Gianfranco Costamagna costamagnagianfra...@yahoo.it wrote:
well, it appeared at the end
Copyright: 2015, Edward Betts
please add your mail
* Gianfranco Costamagna costamagnagianfra...@yahoo.it, 2015-08-20, 10:29:
Pre-Depends: ${misc:Pre-Depends} should be added,
FWIW, ${misc:Pre-Depends} was required for partial squeeze-wheezy
upgrades. It is no longer necessary.
and the dev package should not marked as multiarch same.
Why
Hi, Gianfranco, Julian!
I revised the copyright files, ported some of Julian's work and
generated a new set of debs. You can find them online.
Let me know what to do next.
PS: Note that we have just release OpenSIPS 2.1.1
Thanks a lot for your help!
Răzvan Crainea
OpenSIPS Solutions
On 20-08-15 12:52, Jakub Wilk wrote:
* Gianfranco Costamagna costamagnagianfra...@yahoo.it, 2015-08-20, 10:29:
Pre-Depends: ${misc:Pre-Depends} should be added,
FWIW, ${misc:Pre-Depends} was required for partial squeeze-wheezy
upgrades. It is no longer necessary.
and the dev package
I do remove them now. Not in the previous release where the tarball
was made with make dist (vs github snapshot now).
ok, so it is dfsg, well!
now the changelog has one line extra (line 1)
and maybe you can remove something, like a double
Imported Upstream version 2.3.0+dfsg
(but this is a
Hi,
On 18-08-15 01:01, Tomasz Buchert wrote:
great! Just nit-picking here, really. And trying to understand
AppArmor :).
You seem to be right, I've committed a patch to remove the m flag.
Yes, I tried without postconf present and the unit failed.
Its output is silenced, and postsrsd fails
Le jeu. 20 août 2015 à 0:31, Jerome BENOIT
sphericaltrian...@rezozer.net a écrit :
For something as one week, the current GIT version at Aliot works
great on my box.
(even if the option -u doent work).
Thanks Jerome for testing! I just tried to run chrony with the '-u'
option from
the shell
Hi
On 20-08-15 12:10, Paul Gevers wrote:
Are the man pages regrenerated
Could you check with upstream that he/she really is generating the man
pages by hand in groff format? If not, ask him to include the source.
Are (new) examples installed
Is there a reason why you don't install the
Le jeu. 20 août 2015 à 18:32, Joachim Wiedorn joodeb...@joonet.de a
écrit :
Hello Vincent,
Vincent Blut wrote on 2015-08-20 18:12:
I assume that the change of maintainership has the consent of
Joachim?
Yes, we’ve discussed about this privately some times ago. Still ok
Joachim?
Yes,
Le mer. 19 août 2015 à 21:22, Vincent vincent.deb...@gmail.com a
écrit :
On Tue, 28 Jul 2015 14:18:54 +0200 Vincent Blut
vincent.deb...@free.fr wrote:
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package chrony
* Package name:
On Tue, 28 Jul 2015 14:18:54 +0200 Vincent Blut
vincent.deb...@free.fr wrote:
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package chrony
* Package name: chrony
Version : 1.31.1-1
Upstream Author : Miroslav Lichvar
On Thu, Aug 20, 2015 at 12:29 PM, Gianfranco Costamagna
costamagnagianfra...@yahoo.it wrote:
now the changelog has one line extra (line 1)
and maybe you can remove something, like a double
Imported Upstream version 2.3.0+dfsg
I changed it to avoid confusion.
regarding multiarch
Hi, Gianfranco!
It is not removed - it is still in the sources, but not in the
.orig.tar.gz archive, since I read the upstream tarball should not have
packaging specs inside it.
Should I remove the copyright exception?
Thanks,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com
On
Hi,
It is not removed - it is still in the sources, but not in the
.orig.tar.gz archive, since I read the upstream tarball should not have
packaging specs inside it.
Should I remove the copyright exception?
For Debian sources means the orig tarball, that should be the same as
the upstream
Hi,
I unused-file-paragraph-in-dep5-copyright
paragraph at line 70
I wildcard-matches-nothing-in-dep5-copyright
packaging/gentoo/opensips-*.ebuild (paragraph at line 70)
I guess you removed it?
Julian, how do you feel about it?
cheers,
G.
Il Giovedì 20 Agosto 2015 13:45, Răzvan Crainea
Hello guys,
Right now I am in irc.debian.org at debian-opensis channel, if you
want we can coordinate there.
Kind regards,
2015-08-20 7:53 GMT-05:00 Gianfranco Costamagna costamagnagianfra...@yahoo.it:
Hi,
It is not removed - it is still in the sources, but not in the
.orig.tar.gz archive,
Hi,
A -dev package may contain an architecture dependent -config executable,
that cannot be included in a M-A: same package. The same goes for
headers which vary across architectures.
If there are no architecture dependent files in a -dev package M-A: same
should be fine.
isn't the so link
Hello,
The package fail to build from source:
dpkg-buildpackage: source package opensips
dpkg-buildpackage: source version 2.1.1-1
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Razvan Crainea raz...@opensips.org
dpkg-buildpackage: host architecture amd64
Hello Vincent,
Vincent Blut wrote on 2015-08-20 18:12:
I don’t known why tests have originally been disabled, but I guess
it’s because
they depend on the clknetsim tool which is not packaged in Debian.
Also, if that
tool isn’t installed on the system, the test.common script will try
to
Package: sponsorship-requests
Severity: normal
Dear Vicent and/or other potential sponsors,
I am looking for a sponsor for the latest version of my package roxterm
* Package name: roxterm
Version : 3.1.5-1
Upstream Author : Tony Houghton h...@realh.co.uk
* URL :
Your message dated Thu, 20 Aug 2015 20:56:46 + (UTC)
with message-id 1026269920.8555119.1440104206018.javamail.ya...@mail.yahoo.com
and subject line Re: Bug#796261: RFS: roxterm/3.1.5-1
has caused the Debian Bug report #796261,
regarding RFS: roxterm/3.1.5-1
to be marked as done.
This means
On 2015-08-20 18:33, Thomas Schmitt wrote:
Currently i am stuck at:
- https://wiki.debian.org/DebianMentorsFaq#How_do_I_make_my_first_package.3F
Put a package together, built against a current version of sid.
I'm on Jessie 8.1. The dependencies of the packages in question
are very
* Gianfranco Costamagna costamagnagianfra...@yahoo.it, 2015-08-20, 12:39:
A -dev package may contain an architecture dependent -config
executable, that cannot be included in a M-A: same package.
This particular package doesn't contain any executables, AFAICS.
The same goes for headers which
Hello Vincent,
Vincent Blut wrote on 2015-08-20 18:36:
features. By the way, if I want to close these outdated bug reports,
what’s
the canonical way to do it? I guess I can’t do that from d/changelog?
do it in the changelog: e.g. LP: #1313200
---
Have a nice day.
Joachim (Germany)
On Thu, Aug 20, 2015 at 6:33 PM, Thomas Schmitt scdbac...@gmx.net wrote:
Hi,
i am the upstream developer of freshly orphaned packages
libburn4, libisofs6, libisoburn1, cdrskin, and xorriso.
Now preparing to get them in shape for sponsorship and
for closing old bug reports.
Thanks for taking
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package django-jinja
* Package name: django-jinja
Version : 1.4.1-1
Upstream Author : Andrey Antukh n...@niwi.be
* URL : https://github.com/niwibe/django-jinja
*
On 20-08-15 00:51, Jerome BENOIT wrote:
I keep getting the error message:
Error: Unable to check the signature or the signature was invalid:
== class 'userdir_exceptions.UDFormatError': UDFormatError: Signing key
(80BFC3820C4B26E3, Jerome) has expired
But my key has not expireed. On the
control: owner -1 !
control: tags -1 moreinfo
Hi,
the packaging looks mostly good.
Just a few questions:
python-setuptools (= 0.6b3),
the version is already satisfied in old old stable, you can remove it.
setup.py
install_requiresjinja2 =2.5,
django =1.4,
they aren't listed in B-D, so
Hi Johan
Ok, I will check - some time since I last did this.
ack
Should I do so before uploading to experimental?
nope, experimental will setup an automatic tracker for you, they might even
tell you to go for unstable whenever you like
Looking at the policy I think it is better to
Hi,
i am the upstream developer of freshly orphaned packages
libburn4, libisofs6, libisoburn1, cdrskin, and xorriso.
Now preparing to get them in shape for sponsorship and
for closing old bug reports.
Steve McIntyre offered his help (i hope this means
sponsorship). But knowing how busy he is, i
Le jeu. 20 août 2015 à 13:54, Paul Gevers elb...@debian.org a
écrit :
Hi
Hi again,
On 20-08-15 12:10, Paul Gevers wrote:
Are the man pages regrenerated
Could you check with upstream that he/she really is generating the man
pages by hand in groff format? If not, ask him to include the
Hello Vincent,
Vincent Blut wrote on 2015-08-20 18:12:
I assume that the change of maintainership has the consent of Joachim?
Yes, we’ve discussed about this privately some times ago. Still ok
Joachim?
Yes, that is fully ok.
You make a very good job with maintaining chrony!
Thank you
Hi Jakub,
This particular package doesn't contain any executables, AFAICS.
true
It is now permitted to put architecture-dependent headers files in
/usr/include/triplet, so this is no longer show-stopper.
nice to know :)
If the symlink lives in architecture-specific directory, it's not an
Le jeu. 20 août 2015 à 12:10, Paul Gevers elb...@debian.org a
écrit :
Hi Vincent,
Hello Paul,
Live from Debconf15.
I’m watching you folks, you all look great. :-)
On 19-08-15 21:29, Vincent Blut wrote:
I am looking for a sponsor for my package chrony
Please note this is a first
Your message dated Thu, 20 Aug 2015 16:16:24 + (UTC)
with message-id 369241047.8412344.1440087384911.javamail.ya...@mail.yahoo.com
and subject line Re: Bug#796191: RFS: libharu/2.3.0+dfsg-1~exp1
has caused the Debian Bug report #796191,
regarding RFS: libharu/2.3.0+dfsg-1~exp1
to be marked as
On 20/08/15 13:24, Oxan van Leeuwen wrote:
Hi,
Hi,
On 18-08-15 01:01, Tomasz Buchert wrote:
great! Just nit-picking here, really. And trying to understand
AppArmor :).
You seem to be right, I've committed a patch to remove the m flag.
Ok.
Yes, I tried without postconf present and the
48 matches
Mail list logo
