Gianfranco Costamagna
wrote:
>
> pipeline failed again :/
>
No worried. Only it passes the extract-source phrase. The pipeline was
failed also in the past.
BR,
Bo
>
>
>
>
>
> Il venerdì 31 maggio 2024 alle ore 16:57:24 CEST, Bo YU
> ha scritto:
>
>
>
Merged the two commits
https://salsa.debian.org/ocaml-team/opam/-/merge_requests/10
let me know once you have something that passes pipelines then!
G.
Il venerdì 31 maggio 2024 alle ore 18:35:43 CEST, Gianfranco Costamagna
ha scritto:
Adding it to debian/clean makes the build go to
feel free to address the remaining bits in a
subsequent upload!
G.
Il sabato 1 giugno 2024 alle ore 16:48:27 CEST, Bo YU ha
scritto:
Hi,
On Sat, Jun 1, 2024 at 12:38 AM Gianfranco Costamagna
wrote:
>
> Merged the two commits
> https://salsa.debian.org/ocaml-team/opam/-/mer
Hello,
>hmm, what is wrong with me? My import workflow is below:
>1. git clone xx.git(I forked this one)
>2. gbp pq import
>3. gbp import-orig --pristine-tar --uscan
>4. gbp pq rebase
>5. gbp pq export
>6. commit to master then push
My workflow is:
1. git clone
2. uscan --debug
3. gbp import-orig
control: tags -1 moreinfo
Hello, you are not adding a new changelog entry, but editing the current one.
Please
check the version in sid, and add a new one.
G.
OpenPGP_signature.asc
Description: OpenPGP digital signature
Hello, just add the previous changelog entry, at least we know that something
was in the archive?
G.
Il venerdì 14 giugno 2024 alle ore 10:45:26 CEST, Xiyue Deng
ha scritto:
Hi Gianfranco,
On Sun, 9 Jun 2024 23:58:29 +0200 Gianfranco Costamagna
wrote:
> control: tags -1 morei
Hello,
>Apologies in advance if I am slow to review packages or answer email in the
>next 24 hours-ish. Currently moving from my old daily driver laptop that will
>be now used as a Debian unstable build machine here at home, to my new daily
>driver laptop. Looking forward to seeing what 16 cores (
Hello Phil,
Hi Gianfranco,
As the DD who has taken the package for this upload. If you feel that certain
things can be deferred to a future upload is fine by be.
I usually make exceptions only when the package is already in testing, used by
many people (e.g. in this case, an high popcon), a
control: tags -1 moreinfo
BTW what's the difference with wasi-libc package ?
yeah, looks like the same idea and code, and yet another fork
This branch is 289 commits ahead of, 138 commits behind
WebAssembly/wasi-libc:main.
https://github.com/wasix-org/wasix-libc
https://github.com/WebAssemb
Hello, since no answer was provided to Andreas, and his concern is clear,
I commented out in rules file the removal of COPYING file, and then I sponsored
it.
Attached the new Debian tarball.
G.
On Thu, 5 Sep 2024 13:19:37 +0200 Andreas Ronnquist
wrote:
On Mon, 2 Sep 2024 21:33:32 +0200,
Mate
Hello,
just FYI, the upload fails on i386
https://buildd.debian.org/status/fetch.php?pkg=libcxx-serial&arch=i386&ver=1.2.1-2&stamp=1600846376&raw=0
Due to a difference between i686 and i386
The change in gst-omx might fix this problem
gst-omx (1.18.0-2) unstable; urgency=low
On Thu, 5 Nov 2020 10:43:40 +0100 Gianfranco Costamagna
wrote:
> Hello, thanks!
>
> I was just looking to have the qt fixes uploaded and found your RFS
>
>
unfortunately it turned out to be not sufficient for qt 5.15.1, this additional
patch is required
https://github.com/oli
Hello,
>I'm ready to advocate you
nevermind, looks like you are already doing your AM process :)
good luck!
G.
Il giovedì 12 novembre 2020, 00:27:19 CET, Nicholas D Steeves
ha scritto:
Hi Gianfranco,
Thank you for sponsoring!
Gianfranco Costamagna writes:
> Hello
know your stuff, I never had to change a line on what I sponsor to you...
and when I do it, it turns out its a mistake from my side :p
I'm ready to advocate you
G.
Il giovedì 12 novembre 2020, 00:27:19 CET, Nicholas D Steeves
ha scritto:
Hi Gianfranco,
Thank you for sponsori
Hello,
On Thu, 07 Jan 2021 03:21:51 + Philip Wyett
wrote:
> On Wed, 2021-01-06 at 13:27 +0100, Adam Borowski wrote:
> > On Wed, Jan 06, 2021 at 04:15:28AM +, Philip Wyett wrote:
> > > * Package name: libfilezilla
> > >Version : 0.26.0-1
> > >
> > > It builds those binar
Hello Philip,
while we like to remove non-free stuff from our tarballs, I don't think
removing dlls is a good use case.
Using the upstream tarball is quite convenient, since we have less importing
errors, the md5 is the same
and can be verified, and we don't introduce patches that last forever.
Hello,
>I have an upload stuck in the upload queue due to an expired key, and I
>would like upload my newly unexpired key to the Debian keyservers so
>that it is eventually unblocked.
>
>But I get this error:
>$ gpg -v --keyserver keyring.debian.org --send-key 'fingerprint'
>gpg: sending key 0x t
control: close -1
done thanks
G.
hello,
I can't find the file on mentors...
G.
Il sabato 8 maggio 2021, 10:45:45 CEST, Philip Wyett
ha scritto:
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "libfilezilla":
* Package name : libfilezilla
Version
(already sponsored, nevermind)
Il mercoledì 12 maggio 2021, 11:08:35 CEST, Gianfranco Costamagna
ha scritto:
hello,
I can't find the file on mentors...
G.
Il sabato 8 maggio 2021, 10:45:45 CEST, Philip Wyett
ha scritto:
Package: sponsorship-requests
Severity: n
$CURDIR?
G.
Sent from Yahoo Mail on Android
On Thu, Aug 11, 2022 at 23:21, Ole Streicher wrote: Hi,
one of my packages
https://salsa.debian.org/debian-astro-team/sep
requires to specify a path relative to the package base dir (the path to
a shared library), which is important for build
Hi, I can't yet sponsor your package, but I can give you a quick review.
I honestly do not like custom makefiles, because even if you handle the build
flags, you do not handle e.g. the install DESTDIR
variable and prefix one correctly.
This is why you overridden the dh_auto_install variable.
I
Hi Danny,
(just answering where possible)
>Could you take a look at the debian/watch file? Those opts and regexes
>twisted my mind a bit, not sure if I have done that right.
Please look e.g. at this one
https://sources.debian.net/src/s3cmd/1.5.2-4/debian/watch/
it should be good for you too.
you, they are just nitpicks :)
cheers,
Gianfranco
Il Martedì 4 Agosto 2015 15:03, Gianfranco Costamagna
ha scritto:
Hi Danny,
(just answering where possible)
>Could you take a look at the debian/watch file? Those opts and regexes
>twisted my mind a bit, not sure if I have done that rig
>This is working exactly as intended : )
>
>Try the -f / --full-page command-line switch for "regular" PDFs.
ok, I thought this was a bug... BTW I have the main monitor to the left, and
the extended to the right, why does it show the opposite order for regular pdfs?
>The main feature is the dou
>If you pass no command-line switch it assumes its a double-width pdf,
>which has the "presenter" side on the right and "audience" on the left.
>
>It should™ render the presenter view (with the clocks and the notes) to
>the "primary" screen (you can set with xrandr --output XXX --primary),
>regard
>Well, it is, under the "controls" section. But I guess that's not really
>well-placed, since you didn't find it straight away : )
nope, the manpage is correct, I tried a --help, and I didn't find it
(sorry for the confusion)
>If you have a suggestion on where to place and/or how to re-word the
Other two nitpicks, no need to cc me, I'm subscribed to the list, and
it is called Debian, not debian :)
cheers!
G.
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.o
Hi Danny,
[upstream changes]
nice!
> "is the dbg package working? how can I verify?"
> (too lazy to quote you :) )
$ dpkg -i ../dspdfviewer_1.13.1-1_amd64.deb
[snip]
$ gdb /usr/bin/dspdfviewer
[snip]
Reading symbols from /usr/bin/dspdfviewer...(no debugging symbols found)...done.
$ dpk
Hi Danny
(sending privately)
please do *not* use cdbs :)
It will scare you away!
I do not like it, dh is really better, and fortunately people are switching to
dh :)
cheers,
G.
Il Giovedì 6 Agosto 2015 16:57, Danny Edel ha scritto:
Hello Gianfranco,
On 06/08/15 16:16, Gianfranco
Well now it's public that I do not like cdbs :)
TBH I do not understand it, and the popcon is 1/5 of debhelper.
Two reasons to keep me away from it :)
cheers,
G.
Il Giovedì 6 Agosto 2015 17:18, Gianfranco Costamagna
ha scritto:
Hi Danny
(sending privately)
please do *not* use cdbs :
Hi Ghislain,
I did a quick review of this package, and looks mostly good to me, but I have
some
nitpicks (some errors) for you:
1) you seem to produce a source only library, with no binaries:
- why do you have an arch:any?
2) you seem to disable the testsuite during the build
Hi Tobi, do you plan to do the upload on unstable?
Let me know if I can sponsor the package, seems you already reviewed it ;)
cheers,
Gianfranco
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Ar
Control: tags -1 moreinfo
Hi Tonnerre,
do you still need help?
I would like to see an answer to Jonas on the RC bug you are trying to fix,
do you want to move in a team maintained fashion your package?
Another question is: I see a new release is out, do you plan to package it?
cheers,
Gianfra
Control: tags -1 moreinfo
Hi Bastien,
security uploads needs usually an ack from Security Team, did you already
receive that'
Second: you asked to upload for stable, oldstable and o-o-stable, but the
debdiff is only against stable.
Does the debdiff applies to the other two suites too?
Let me
Control: tags -1 moreinfo
Hi Antti,
I did a quick review of the package, since it should be time for
an unstable upload.
Some nitpicks (and some showstoppers to me):
1) d/changelog: please update the changelog to point to unstable suite
(maybe also refresh the timestamp)
2) d/changelog might b
Hi Ghislain,
>I did not expect a review so soon, many thanks!
sorry to ruin your Saturday :)
>Should be arch:all indeed.
ack
>That one is a bit difficult. It is temporarily disabled because at the
>time v0.4 was released the test suite was quite buggy and most tests
>failed. According to t
Hi Ghislain,
the package looks good!
There still are some copyright issues: e.g.
licensecheck cmake/FindTBB.cmake
cmake/FindTBB.cmake: MIT/X11 (BSD like)
seems that you missed one :)
cheers (sorry for noticing only now)
G.
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian
Hi Antti,
>Not changed yet, but inquiry sent to
>http://lists.alioth.debian.org/cgi-bin/mailman/private/pkg-qemu-devel/2015-August/006604.html
>so if they have good suggestions, then one more upload to mentors
>will be needed.
I can't/won't read, but ok, it is good as-is, let me know if you
Hi,
sorry for top posting, I'm on mobile.
can you please try to look at
virtualbox-ext-pack and see if it fits your needs?
It is a package that downloads stuff from the internet after showing you a
license and asking to accept it.
cheers,
G.
--
Il lun 10 ago 201
Hi Daniel,
>I've rewritten deb/control and deb/rules to build with two packages, for Py2
>and Py3.
>
>Fresh mentors upload is available.
>
>New buildlog:
>http://www.danielstender.com/buildlogs/python-afl_0.2.1-1_amd64-20150809-2223.build
I did a look, and the packaging looks really good (and t
Control: owner -1 !
Hi,
>Changes since the last upload:
> * New upstream release.
> * Add patch 01: use /dev/urandom instead of /dev/random in test 20
>to prevent lengthy delays during build.
Hi, I'm doing a test build right now, I'll see how it goes and report back :)
The packaging look
Hi Lucas
(sorry for not answering on irc, I was AFK)
hardening-check debian/xmbmon/usr/bin/xmbmon
d/rules:
override_dh_auto_build:
$(MAKE) CFLAGS="$(CFLAGS)" CPPFLAGS="$(CPPFLAGS)" CXXFLAGS="$(CXXFLAGS)"
LDFLAGS="$(LDFLAGS)"
something like this seems to make autoconf aware of the flags (not
Hi
>My name is Razvan Crainea[1] and I am one of the Core developers of the
>OpenSIPS project, a Voice-over-IP SIP server. We would like our project
>to be added to the official Debian repository and we need a mentor to
>help us achieve this.
>We already have some DEB packages for OpenSIPS th
Hi again,
>8) debian/control
> - please bump std-version to 3.9.6
> - please remove the conflicts
>(<< ${binary:Version})
and please remove yourself from uploaders, you are already maintainer :)
cheers,
G.
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a su
8-11 21:05 GMT+08:00, lucas castro :
> Gianfranco,
> No problem about about that on irc.
> I think I should take a time on another package, then mailed here.
> and if anyone know about this, it's fine. I really spent much time on this
> package,
> and learned a lot with it.
&g
Control: owner -1 !
Hi Johan,
the package looks good.
Some nitpicks,
1) please do not usee the © symbol in debian copyright(I remember there were
issues with machine readable format and that symbol)
2) licensecheck says:
click_plugins/__init__.py: BSD (2 clause)
but seems that it is actual
Control: owner -1 !
Hi Peter
some comments
1) d/changelog:
sndio (0.0.10-1) UNRELEASED; urgency=low
(feel free to spot the error :) )
2) d/rules:
I would prefer to run dh_auto_configure -- instead of ./configure
but it should be the same...
(actually dh_auto_configure fails, because it adds
Hi Zhou,
General Note: I don't think I'll sponsor this package without a discussion on
debian-devel mail list,
because I do not honestly think we need another package management, specially
because
mixing stuff might lead to libraries incompatibilities, and something more.
Do you install so
Hi Victor,
some spurious commenting
(not a perl user, so I can't help in sponsoring)
d/control: debhelper >=9 might be better
perl, perl (>= 5.13.11) | libtest-simple-perl (>= 0.98)
seems hacky, but I understand simple-perl might be needed only for older perl
releases
(note: I'm not sure bu
>
>For perl arch:all packages there are no relevant changes between
>debhelper compat level 8 and 9.
>But yes, it at least makes lintian (with its new pedantic warning)
>happy.
exactly :)
>That's perfectly fine, is used all over the place in perl packages
>and works.
so my guess was true, wo
Hi Adrien
I see the package is already sponsored,
anyway I would like to ask you to update the copyright file, since it seems a
little bit
outdated :)
BTW the ubuntu patch might be good to be in Debian too, maybe disabled
(does Debhelper supports something like "apply this patch if Ubuntu is
Hi Răzvan,
thanks for the fixes,
mentors is showing many lintian errors...
can you please fix them?
reporting them here:
>E copyright-should-refer-to-common-license-file-for-gpl
>W hardening-no-relro
>I hardening-no-fortify-functions
(usually fixed by not overriding C*FLAGS and LDFLAGS
>I
cause you need to make your compiler
aware of the location and use it.
that was my question at the begin.
>
>I will do dch -r when confirmed that this package is really ready
>to be uploaded.
ok
>
>Yes, indeed I should provide a manpage for /usr/bin/linuxbrew
>and merly overr
Well, race conditions happens!
No problem, thanks Andreas for taking care of the upload then :)
(BTW the problem was actually that I had to build and review the packaging,
specially for the multiarch part, and it took me some time :) )
cheers,
G.
--
Il dom 16 ago 2
control: owner -1 !
Hi Andreas,
let's review:
1) please use a machine-readable copyright file
http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
2) d/compat: please bump to 9
3) d/control: you might want to run wrap-and-sort to clean the formatting up,
to bump debhelper to >=9 and
Hi Lumin
>Such "packaging bug" is upstream bug, and is handled by Homebrew
>and Linuxbrew upstream. And files made that trouble was not provided
>by Debian package ..
yes, exactly the point I had, so somewhere the user should be aware that
reporting
the bug on Debian Bug Tracking System i
Hi Lumin,
>I didn't mean "overriding the env is bad". I mean:
>-> can we directly add ENVs for users?
> -> how about doing this in wrapper script:
> sed -i -e "$a\$(cat /usr/share/.../example/profile)" .bashrc
> -> very bad.
>Then can ENVs be handled automatically?
>
>Then there are 2 th
Control: owner -1 !
Hi Adrien, I did have some problem in recreating the pristine tarball,
I had to change back on changelog, and control the source name, and then
git-buildpackage didn't
fail anymore
(and to move back the orig tarball of course)
Built&Signed&Uploaded on experimental and tagged
Control: owner -1 !
Hi Markus,
Following my review:
1)
# upstream does not sign releases
#yadifa source: debian-watch-may-check-gpg-signature
ls upstream/signing-key.asc
upstream/signing-key.asc
which one is correct?
2) sbin/yadifad/install-sh
not mentioned in copyright
(and every insta
Hi Lumin,
some new stuff
(btw feel free to discuss on -devel, there is no need to have a perfect package
for the discussion)
d/changelog should mention only initial release (closes: #) and nothing
more.
debian/linuxbrew-wrapper.lintian-overrides
useless now?
debian/copyright, please rethi
http://mentors.debian.net/package/opensips
Many thanks,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com
On 08/14/2015 10:41 PM, Gianfranco Costamagna wrote:
> Hi Răzvan,
>
> thanks for the fixes,
>
> mentors is showing many lintian errors...
>
> can you please fi
ct (I
was using an older lintian version), but I will work on fixing those too.
Best regards,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com
On 08/18/2015 05:11 PM, Gianfranco Costamagna wrote:
> Hi,
>
> unfortunately the upload seems to be missing
> Uploaded:
Control: owner -1 !
Lets review:
1) debian/changelog should only contain one entry.
Initial release (Closes: #ITPBUG)
2) debian/control: debhelper >=9 is recommended
3) d/control: "python-pyinotify, python-boto, python-dateutil, python-argparse"
they are all listed in setup.py install_requires
Hi
>
>the issue comes from patch: add-license-info.patch
>
>The patch is patching author's source files with author's original
>copyright declaration in the "global" LICENSE file and the one
>in head of progress.c . The patch was sent to author days ago
>and we (Asias and me) are waiting for au
Hi Lumin,
>I have just uploaded a updated package to mentors several seconds ago,
>and I will CC you later in the d-devel discussion.
thanks but I already follow -devel :)
>If I don't write them in dch, even I will forget what I've done to
>the package months later.
>
>Policy chapter 4.4 said
Hi
>W debian-watch-file-in-native-package>* You asked me to add a watch file, but
>I created a native
>package. Should I remove the file?
why? don't you have an orig tarball to start from?
http://opensips.org/pub/opensips/latest/src/
just use quilt source format, and make the vcs point to
Hi Jeremy,
>I've started by branching upstream and getting the scripts to pass 2to3,
>but those are breaking changes... I'm not exactly sure how I'd include
>these in the package while still maintaining compatibility with Python
>2.
you can run 2to3 or 3to2 (both available on Debian) during bui
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com
On 08/19/2015 04:14 PM, Gianfranco Costamagna wrote:
> Hi
>
>
> W debian-watch-file-in-native-package>* You asked me to add a watch file, but
> I created a native
> package. Should I remove the file?
>
&g
Kimiki review:
please fix all the above (message #72 of bug 772823)
d/changelog: no need to put your name into []
when you are the only one who worked on the package (and the signature
is your)
d/rules: as said skipping tests is usually bad, please enable them if possible
d/copyright: "multip
sphde:
d/changelog: please set to "unstable" the target series
d/control: what about having the doxygen documentation in a -doc package
arch=all with doxygen moved to build-depends-indep?
look e.g.
https://sources.debian.net/src/websocketpp/0.6.0-1/debian/control/
and the rules file
(note, you
nings
disappear)
thanks a lot,
Gianfranco
Il Mercoledì 19 Agosto 2015 18:34, Gianfranco Costamagna
ha scritto:
Hi,
I didn't have time for a complete review, but two things needs to be fixed:
some copyrights are missing, ISL and some BSD2 IIRC
(I did a licensecheck * -r)
changelog s
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: 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_requires"jinja2 >=2.5",
"django >=1.4",
they aren't listed in B-D
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 mentione
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 docu
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.
Built&Signed&Uploaded, thanks for your contribution to Debian!
cheers,
G.
Il Giovedì 20 Agosto 2015 11:54, Edward Betts ha scritto:
Gianfranco Costamagna wrote:
> well, it appeared at the end
>
> "Copyright: 2015, Edward Betts"
> please add your mail
Done.
>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
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 l
nSIPS Solutions
www.opensips-solutions.com
On 08/19/2015 09:14 PM, Gianfranco Costamagna wrote:
> BTW I would like to have a rules file with plain dh_ calls, can you please
> try to use the rules file from julian's svn?
>
> you can compare the output of two builds with debdiff if nee
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 upstr
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/, so this is no longer show-stopper.
nice to know :)
>If the symlink lives in architecture-specific directory, it's not an
>is
rebuild,
ongoing right now)
How do you feel about updating afl, checking if everything is good and then
followup with python-afl?
cheers,
Gianfranco
Il Lunedì 10 Agosto 2015 11:36, Daniel Stender ha
scritto:
On 10.08.2015 11:04, Gianfranco Costamagna wrote:
> I did a look, and
Hi Alex,
let's review :)
d/changelog please set to unstable, and update the timestamp
d/rules: wl-asneeded is good if enable, does it introduce some problems?
are both autotools-dev and autoreconf needed?
usually the latter should superceed the former
d/rules: I personally do not like calling "bo
Hi
>Okay. I think this needs further explaination. Upstream does not
>include a build system, not even a Makefile. Building is done by
>invoking gcc directly using different flags for different platform.
>This is however cumbersome, so I add autotools to ease building. I use
>git for development
Hi,
>Actually no. I think this needs clarification. The upstream tarball
>contains .c .h files and some (non-dfsg-compliant) temporary files.
>The repack script removes the (non-dfsg-compliant) temporary files and
>move all the .c .h files into a directory called src/. The build
>system and frien
Hi,
>W: paflib source: changelog-should-mention-nmu
if you are nmuing it you need to mention the Non-maintainer upload
in changelog.
dch --nmu (or similar) does it for you
>W: paflib source: source-nmu-has-incorrect-version-number 0.2.0-1
same here, 0.2.0-1 is not an NMU number, 0.2.0-1.1 is
Hi,
>Ok, I've tested on a clean jessie install and the systemd script works
>as expected. I also made sure this package will build properly against
>sid.
wonderful
>The python-3to2 packages does not appear to exist in jessie, only
>stretch and sid. 3to2 is not installed by the python package in
>Did you mean to close the bug?
nope, sorry
>About the dep5 copyright issue, yes, I accidentally left out the header.
no problem
>I will fix the use-flag patch as you described.
ok
(this shouldn't change anything, since LDFLAGS in this case are the Debian
flags,
and for sure they do not add
Hi Alex,
>I contacted Ernst (upstream dev) and he agreed to integrate the build
>system into his dev branch.
Wonderful! Good news are good :)
>I think the above should solve the version string problem as well. Or
>if it doesn't we can use the old method based on date string. I think
>it should
Hi Thomas
>So this in libburn4.install:
>
> debian/tmp/usr/lib/*/libburn.so.4*
>
You can just say usr/lib/*/libburn.so.4*
or even better
usr/lib/*/libburn.so.*
that way at the next soname bump you won't need
to change the install files too.
($somebody might object that having the 4 makes yo
Hi again Thomas,
>I've uploaded a new version to mentors fixing all the problems described
>above/below.
yes, mostly done I see just some issues left:
1)
> * Update debian/changelog to conform to DEP5
I guess you didn't mean changelog :p
2)
About the cmake file, please answer.
I really do n
Hi Andreas,
>thanks again for your review. I have uploaded dblatex-0.3.7-2 to
first nitpick: not needed to upload a -2 version. using the same -1
is fine and works until the real upload (on Debian ftp-master) is
performed
>Sorry to disagree with your first suggestion (terrible start, I know)
Hi Thomas,
(please open an RFS if you need a sponsor, otherwise it might be difficult
to track packages reviews and to actually have an upload)
>There will be no SONAME change as long as i am the upstream
>developer. ABI compatibility is one of the most important
>goals of my development.
this
Hi Thomas,
If you dput $something, you need to wait until $something is processed,
any later upload will fail because you can't overwrite the files
in ftp unprocessed queue.
So wait for the upload, get the email confirmation, and then dput again.
According to the log you posted, seems that dpu
Control: owner -1 !
Control: tags -1 moreinfo
Hi Ross!
The packaging looks really good to me, just a problem on VCS.
DPMT recently rejected my application, so I had to reupload everything
with VCS pointing to collab-maint,
so I'll happily sponsor the package once your application gets approved.
Hi Jeroen,
the package right now is really not suitable for unstable
You can see the lintian warnings errors on the mentors package page.
Can you please fix them?
also the changelog should mention "Initial Release: Closes #WNPPBUG)
and the target shouldn't be "UNRELEASED"
note, many lintian s
701 - 800 of 1488 matches
Mail list logo
