-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Arno,
> did you try to contact your previous sponsors? Could you reach Hauke?
Not yet, I will try to contact them and get back to this thread if none
of the previous sponsor has time for an upload.
>> This version includes a little bugfix and upd
Hi,
On 19.08.2012 12:38, Werner Detter wrote:
> I've recreated a new version of my package policyd-weight (previous version
> 0.1.15.2-2 was already
> uploaded to unstable.
did you try to contact your previous sponsors? Could you reach Hauke?
> This version includes a little bugfix and updates
On 02/17/2012 03:13 AM, Werner Detter wrote:
>> Did you ask zigo who sponsored your last upload?
>>
> sure i did. But he just became a father so he had no time left for uploading
> the package.
>
Also, I'm busy with other packages, and did that last upload
because I thought it was importan
Hi,
>> The sponsoring game in Debian is a game of patience[1].
As the process is pretty new and I'm not (yet) familiar with "normal" time
slots for
sponsored uploads this is something learned. Thomas helped me a lot for which
I'm
really grateful, working with him is fun and it went fast. I've
Hi,
> The sponsoring game in Debian is a game of patience[1]. Sending an email
> every two days telling you are waiting for an upload doesn't do much
> more than annoy the very few people that are keen on sponsoring
> packages.
It's not my first sponsored upload but the second one. The first one
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
>> so, it seems to me as nobody cares about uploading this package (and it's
>> really just the upload) Well, I've done my Job. I can't do more
>> then asking for a sponsor that will upload the package Meanwhile I'm
>> thinking about
On Thu, 16 Feb 2012, Werner Detter escribió:
> Hi,
>
> so, it seems to me as nobody cares about uploading this package (and it's
> really just the
> upload) Well, I've done my Job. I can't do more then asking for a
> sponsor that will
> upload the package Meanwhile I'm thinking about
On Thu, Feb 16, 2012 at 04:41:39PM +0100, Werner Detter wrote:
> so, it seems to me as nobody cares about uploading this package (and it's
> really just the
> upload) Well, I've done my Job. I can't do more then asking for a
> sponsor that will
> upload the package Meanwhile I'm thinkin
Hi,
Please do not top-post.
Le 16/02/2012 à 16:41, Werner Detter écrivit :
> > Dear mentors,
> >
> > I've recreated a new version of my package policyd-weight (previous version
> > 0.1.15.2-1 was already
> > uploaded to unstable. This version includes another bugfix, delivers the
> > /etc
Hi,
so, it seems to me as nobody cares about uploading this package (and it's
really just the
upload) Well, I've done my Job. I can't do more then asking for a sponsor
that will
upload the package Meanwhile I'm thinking about orphaning the package if
it's always
the same procedure of
Anyone ? :)
Am 08.02.12 12:53, schrieb Werner Detter:
> Hi everybody
>
> I've received an email from Thomas. He proposed that it would make sense to
> have not only one sponsor for my package but maybe two So if one is busy
> the other one can do the sponsoring.
>
> Thomas had no time to uploa
Hi everybody
I've received an email from Thomas. He proposed that it would make sense to
have not only one sponsor for my package but maybe two So if one is busy
the other one can do the sponsoring.
Thomas had no time to upload my package which I've uploaded on Januar 24th.
But he suggested to a
Hi Arno,
thanks for the hint. I will get back to Zigo directly. Sorry for
the noise caused and have a nice weekend.
Cheers,
Werner
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Werner,
On 14.01.2012 15:15, wer...@aloah-from-hell.de wrote:
> I've recreated a new version of my package policyd-weight (previous version
> 0.1.15.2-1 was already
> uploaded to unstable. This version includes another bugfix, delivers the
> /
Hi Ansgar,
> sorry that I could not look at your package even after I said that I
> would earlier, but I did not have enough free time. But it was uploaded
> in the end anyway :)
No problem - I've just fixed another bug (#641538) in my local packet.
> It is not possible to change the package a
Hi,
sorry that I could not look at your package even after I said that I
would earlier, but I did not have enough free time. But it was uploaded
in the end anyway :)
wer...@aloah-from-hell.de writes:
> Could you please re-upload the package? I've just uploaded the latest
> version to mentors. So
On 01/08/2012 10:27 PM, wer...@aloah-from-hell.de wrote:
> Hi,
>
> can anyone re-upload the package ? :)
>
> regards,
> Werner Detter
http://qa.debian.org/developer.php?login=wer...@aloah-from-hell.de
It's in, as you can see!
I don't think re-uploading only for the /etc/default/policyd-weight
is
On 01/06/2012 09:32 PM, wer...@aloah-from-hell.de wrote:
> Hi Thomas,
>
> I've received an email from Debian FTP-Masters with the information that the
> package got
> rejected:
>
> ---
> Reject Reasons:
> policyd-weight_0.1.15.2-1_all.deb: deb contents timestamp check failed [ 'exceptions.NameErro
Hi,
can anyone re-upload the package ? :)
regards,
Werner Detter
Am 07.01.12 11:45, schrieb wer...@aloah-from-hell.de:
> Dear Mentors,
>
> I've just installed my policyd-weight package from unstable. There my
> /etc/default/policyd-weight file is not created, currently I'm not sure
> if the ver
Dear Mentors,
I've just installed my policyd-weight package from unstable. There my
/etc/default/policyd-weight file is not created, currently I'm not sure
if the version that has been uploaded to mentors does include the
/etc/default/policyd-weight file already so I've downloaded the source
and i
Hi Arno,
>> a) it's ok that the files reside in the debian directory ?
>> b) I missed a "dh_clean" (or pedant) somewhere ?
>> c) I have to delete those manually?
>
> I didn't actually try your source package, but it looks feasible. These
> files are created by a regular build process and entirely
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Werner,
On 06.01.2012 21:24, wer...@aloah-from-hell.de wrote:
> a) it's ok that the files reside in the debian directory ?
> b) I missed a "dh_clean" (or pedant) somewhere ?
> c) I have to delete those manually?
I didn't actually try your sourc
Hi again,
I do have another question left.
I've just discovered that there are some files left in the debian directory
after package
creation, e.g.
debian/files
debian/policyd-weight.*
debian/policyd-weight.*.debhelper
debian/*.dephelper.log
debian/policyd-weight/
As source packages should not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06.01.2012 14:45, wer...@aloah-from-hell.de wrote:
>> That seems to be a bug in in dak to me. I've tried to ask relevent
>> persons, maybe they can help you out.
Mark fixed a bug in dak which produced your faulty error message. The
problem was the
Hi Arno,
> That seems to be a bug in in dak to me. I've tried to ask relevent
> persons, maybe they can help you out.
OK, thank you :)
Have a nice day,
Werner
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06.01.2012 14:32, wer...@aloah-from-hell.de wrote:
> What's wrong?
That seems to be a bug in in dak to me. I've tried to ask relevent
persons, maybe they can help you out.
- --
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuP
Hi Thomas,
I've received an email from Debian FTP-Masters with the information that the
package got
rejected:
---
Reject Reasons:
policyd-weight_0.1.15.2-1_all.deb: deb contents timestamp check failed [: global name 'MTime' is not defined]
---
What's wrong?
Thanks,
Werner
--
To UNSUBSCRIBE,
Hi Thomas,
> I'd add a file there, with lots of comments, and all the options that
> you can put in it. It doesn't mater if absolutely every options are
> commented out, the point is to document what can be done with
> useful comments.
>
> Maybe you can do that on your next upload?
done :) I've
On 01/06/2012 07:44 PM, wer...@aloah-from-hell.de wrote:
> Hi Thomas,
>
> thanks for your helpfull comments.
>
>
>> What was in /etc/default/policyd-weight? Why aren't you using
>> it anymore?
>>
> It behaves like the current package in unstable/testing/stable.
> The file /etc/default/polic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Werner,
On 06.01.2012 13:32, wer...@aloah-from-hell.de wrote:
> I think that's the way to go. But where in source package should i put
> the file in my source package? I would then copy the file by postinst
> to /etc/default/policyd-weight ?
ty
Hi Arno,
> there is a slight disagreement between several positions within Debian
> regarding /etc/default/daemon options. That's confusing and something we
> should work on, but that needs to be addressed at a higher level.
Ok, i see.
> For you, in particular, you can choose either alternative
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Werner,
On 06.01.2012 12:44, wer...@aloah-from-hell.de wrote:
> What should we do here? Generate the file? Or don't take account of
> it in the init script?
there is a slight disagreement between several positions within Debian
regarding /etc/d
Hi Thomas,
thanks for your helpfull comments.
> What was in /etc/default/policyd-weight? Why aren't you using
> it anymore?
It behaves like the current package in unstable/testing/stable.
The file /etc/default/policyd-weight isn't created but the init
script takes account of it.
/etc/default/po
On 01/06/2012 01:14 PM, Thomas Goirand wrote:
> Your debian/init.d script shouldn't set the PATH at all.
> All the folders it is putting in PATH are already accessible
> in the default $PATH, so don't change it.
>
FYI, pabs don't agree with me, and think declaring the $PATH
is the way to go. So
On 01/06/2012 02:07 AM, wer...@aloah-from-hell.de wrote:
> Dear mentors,
>
> I am looking for a sponsor for my package "policyd-weight".
>
> * Package name: policyd-weight
>Version : 0.1.15.2-1
>Upstream Author : Robert Felber
> * URL : www.policyd-weight.org
> *
* Thomas Goirand , 2012-01-05, 18:10:
seems like this entry in debian/rules fixed it :)
clean:
rm -fr debian/files
dh_clean
*NO* !!! :)
You really need the dh_testdir and dh_testroot calls.
dh_testdir and dh_testroot act only as extra safety nets. Their use is
certainly not
On 12/30/2011 06:30 AM, wer...@aloah-from-hell.de wrote:
> seems like this entry in debian/rules fixed it :)
>
> clean:
> rm -fr debian/files
> dh_clean
>
*NO* !!! :)
You really need the dh_testdir and dh_testroot calls.
Thomas
--
To UNSUBSCRIBE, email to debian-mentors-requ.
On 12/30/2011 05:54 AM, wer...@aloah-from-hell.de wrote:
> With:
>
> # include /usr/share/quilt/quilt.make
> # clean: unpatch
> clean: dh_testdir
> dh_testroot
> dh_clean build-stamp
>
> I get:
> dpkg-buildpackage: source package policyd-weight
> dpkg-buildpackage: source version 0.
Dear mentors,
sorry that I've created two threads for my package. Please correspond on this
thread to avoid confusion. All comments from mentors have been considered,
the latest package is clean and awaits a sponsor :)
thank you,
Werner Detter
--
To UNSUBSCRIBE, email to debian-mentors-requ...
Hi all,
just check the package, this thread here is already done :) So it makes no
sense to comment stuff that's already fixed.
thank you,
Werner
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
A
Hi Ansgar,
>>> And the version with unpatch and the include removed? From the error I
>>> suspect you moved the dh_testdir one line up behind the clean.
>>
>> With:
>>
>> # include /usr/share/quilt/quilt.make
>> # clean: unpatch
>> clean: dh_testdir
>> dh_testroot
>> dh_clean buil
Dear mentors,
I am looking for a sponsor for my package "policyd-weight".
* Package name: policyd-weight
Version : 0.1.15.2-1
Upstream Author : Robert Felber
* URL : www.policyd-weight.org
* License : GPL-2+
Section : mail
It builds those binar
Hi again :)
> Best is to create a patch, include it in your Debian package, and forward
> that patch to upstream so he can have his manpage fixed upstream as
> well (so you will later remove the debian-specific patch).
I've created a new Patch which fixes the spelling errors and mentioned that
in
Am Dienstag, den 03.01.2012, 04:10 +0800 schrieb Thomas Goirand:
> > OK, got it *but* what revision do i have to use?
> > http://anonscm.debian.org/viewvc/dep/web/deps/dep5.mdwn?revision=?
> >
> > Thanks,
> > Werner
>
> As per:
> http://anonscm.debian.org/viewvc/dep/web/deps/dep5/
>
> t
On 01/03/2012 03:03 AM, wer...@aloah-from-hell.de wrote:
> Thanks for the hint. How do you handle spelling errors by the upstream
> author in the relevant manpages? Should i create patches for it? How's
> the workflow handling spelling errors by the upstream author?
>
Best is to create a patch,
Hi Thomas,
> * Your debian/copyright doesn't mention yourself, I think
> you should add yourself in the Files: debian/*. The
> debian/copyright is also badly formatted, and generally
> speaking seems to be using a very old definition of the
> DEP5 specifications. It'd be great if you could update
On 01/03/2012 03:02 AM, wer...@aloah-from-hell.de wrote:
> Hi,
>
>> * Your debian/copyright doesn't mention yourself, I think
>> you should add yourself in the Files: debian/*. The
>> debian/copyright is also badly formatted, and generally
>> speaking seems to be using a very old definition of the
Hi,
> As per:
> http://anonscm.debian.org/viewvc/dep/web/deps/dep5/
>
> the latest revision seem to be 240.
Thanks, that worked for me :)
Cheers,
Werner
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debi
Hi,
> ntian with the options -Ii -E --pedantic so it
> will show you more issues (like spelling mistakes in the
> man pages, etc.). I wont details them here, since Lintian
> does it better than me! :)
Thanks for the hint. How do you handle spelling errors by the upstream
author in the relevant ma
Hi,
> * Your debian/copyright doesn't mention yourself, I think
> you should add yourself in the Files: debian/*. The
> debian/copyright is also badly formatted, and generally
> speaking seems to be using a very old definition of the
> DEP5 specifications. It'd be great if you could update that.
Hi Thomas, hi Ansgar,
thanks for the hints. I will improve the package as suggested by you and
let you know when I'm done :)
Cheers,
Werner
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
Hi,
Since I might be interested in using this software, I had
a quick look to the packaging. I've noticed some issues
that are remaining. Ansgar, feel free to correct me if you
don't agree with my remarks!
* Please run lintian with the options -Ii -E --pedantic so it
will show you more issues (li
Hi Ansgar,
thanks - again :)
> It looks okay, but you should no longer need neither the build
> dependency on quilt (the include in d/rules is gone) nor the
> d/README.source (it's a standard format and d/changelog already mentions
> it was deleted).
deleted quilt dependency, deleted debian/READ
wer...@aloah-from-hell.de writes:
> I've recreated and reuploaded the package.
It looks okay, but you should no longer need neither the build
dependency on quilt (the include in d/rules is gone) nor the
d/README.source (it's a standard format and d/changelog already mentions
it was deleted).
Ther
Hi Ansgar,
thank you for your hints.
> Why do you list temporary files in debian/source/include-binaries? They
> should be removed by the clean target (dh_clean).
You're right. I just forgot to remove the file. Fixed.
> Keeping dh_testdir in the clean target also should not hurt.
Thanks. Added
wer...@aloah-from-hell.de writes:
>> And the version with unpatch and the include removed? From the error I
>> suspect you moved the dh_testdir one line up behind the clean.
>
> With:
>
> # include /usr/share/quilt/quilt.make
> # clean: unpatch
> clean: dh_testdir
> dh_testroot
> d
Hi,
wer...@aloah-from-hell.de writes:
> I am looking for a sponsor for my package "policyd-weight".
> dget -x
> http://mentors.debian.net/debian/pool/main/p/policyd-weight/policyd-weight_0.1.15.2-1.dsc
Why do you list temporary files in debian/source/include-binaries? They
should be removed b
Dear mentors,
I am looking for a sponsor for my package "policyd-weight".
* Package name: policyd-weight
Version : 0.1.15.2-1
Upstream Author : Robert Felber
* URL : www.policyd-weight.org
* License : GPL-2+
Section : mail
It builds those binar
Hi Jakub,
> dh_clean does remove debian/files, you don't need that explicit rm -fr.
good to know, thanks. Fixed, recreated and uploaded again on mentors.
thank you,
Werner Detter
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Cont
clean:
rm -fr debian/files
dh_clean
dh_clean does remove debian/files, you don't need that explicit rm -fr.
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: h
Hi,
> dpkg-genchanges: warning: duplicate files list entry for file
> policyd-weight_0.1.15.2-1_all.deb (line 7)
> dpkg-genchanges: warning: duplicate files list entry for file
> policyd-weight_0.1.15.2-1_all.deb (line 8)
> dpkg-genchanges: including full source code in upload
>
> Every time I
Hi,
the package is built by using "clean:" without any parameters but if gives me
warnings like follows:
dpkg-genchanges -sa >../policyd-weight_0.1.15.2-1_amd64.changes
dpkg-genchanges: warning: duplicate files list entry for file
policyd-weight_0.1.15.2-1_all.deb (line 2)
dpkg-genchanges: warni
Hi,
> And the version with unpatch and the include removed? From the error I
> suspect you moved the dh_testdir one line up behind the clean.
With:
# include /usr/share/quilt/quilt.make
# clean: unpatch
clean: dh_testdir
dh_testroot
dh_clean build-stamp
I get:
dpkg-buildpackage
wer...@aloah-from-hell.de writes:
>> How did your rules file look like?
> Currently:
[...]
> include /usr/share/quilt/quilt.make
> clean: unpatch
> dh_testdir
> dh_testroot
> dh_clean build-stamp
And the version with unpatch and the include removed? From the error I
suspect you
Hi,
> How did your rules file look like?
Currently:
#!/usr/bin/make -f
# written by Jan Wagner
#
# Uncomment this to turn on verbose mode.
#export DH_VERBOSE=1
include /usr/share/quilt/quilt.make
clean: unpatch
dh_testdir
dh_testroot
dh_clean build-stamp
install: buil
Hi,
wer...@aloah-from-hell.de writes:
+include /usr/share/quilt/quilt.make
+build-stamp: $(QUILT_STAMPFN)
clean: unpatch
>>> I had to leave the line "include /usr/share/quilt/quilt.make" otherwise
>>> the package build fails.
>>
>> With what error? I guess you did not remove the "u
Hi,
I've added comments to my quilt patches and reuploaded the source package.
So there is stuff left:
+include /usr/share/quilt/quilt.make
+build-stamp: $(QUILT_STAMPFN)
clean: unpatch
>>> I had to leave the line "include /usr/share/quilt/quilt.make" otherwise
>>> the package bu
Hi,
> wer...@aloah-from-hell.de writes:
>>> +include /usr/share/quilt/quilt.make
>>> +build-stamp: $(QUILT_STAMPFN)
>>> clean: unpatch
>> I had to leave the line "include /usr/share/quilt/quilt.make" otherwise
>> the package build fails.
>
> With what error? I guess you did not remove the "unpatc
wer...@aloah-from-hell.de writes:
>> +include /usr/share/quilt/quilt.make
>> +build-stamp: $(QUILT_STAMPFN)
>> clean: unpatch
> I had to leave the line "include /usr/share/quilt/quilt.make" otherwise
> the package build fails.
With what error? I guess you did not remove the "unpatch" dependency f
Dear Ansgar,
thanks for your helpfull reply. I have some more questions.
> >From d/changelog:
>
> ++ * New upstream release
> ++- (Closes: #641227)
>
> The second line misses something behind the dash.
Changed.
> There is a debian/.pc directory which should not be there.
Removed.
> You sho
Ansgar Burchardt writes:
> You should mention that the package has a new maintainer and close the
> bug indicating that the package is orphaned (#612734).
Oh, I forgot: you also should retitle the bug from "O (orphaned)" to
"ITA (intend to adopt)" and set yourself as owner.
Regards,
Ansgar
--
Hi,
wer...@aloah-from-hell.de writes:
> I am looking for a sponsor for my package "policyd-weight".
[...]
> dget -x
> http://mentors.debian.net/debian/pool/main/p/policyd-weight/policyd-weight_0.1.15.2-1.dsc
>From d/changelog:
++ * New upstream release
++- (Closes: #641227)
The second
* Ansgar Burchardt , 2011-12-25, 19:43:
Stable is frozen, we do not change packages there unless there is a
very good reason to do so. The bug you are fixing does not seem to
qualify as release critical thus we need to deal with the problem as is.
OK, thanks for your details. I do also think, th
wer...@aloah-from-hell.de writes:
>> Stable is frozen, we do not change packages there unless there is a very
>> good reason to do so. The bug you are fixing does not seem to qualify as
>> release critical thus we need to deal with the problem as is.
>
> OK, thanks for your details. I do also think
Hi Arno,
> well, you're presumably the new maintainer. Hence it is up to you to
> package new versions whenever that seems feasible to you. Generally you
> should try to keep track with upstream so yes, package the new version
> by evolving the latest source package available in Sid.
The current
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Werner,
On 25.12.2011 16:43, wer...@aloah-from-hell.de wrote:
> "A new upstream version is available: 0.1.15.2, you should consider packaging
> it."
> Should i package the new version available or should i repack the current one
> from unstable?
Hi Arno,
> we're developing towards Unstable only. Thus, if you want to take over
> as a maintainer of a package your work is always invested in Unstable.
>
> In your case the package is orphaned, hence you can just take over it.
> Use the latest source package available in Debian Unstable, packag
Hi Arno,
> In your case the package is orphaned, hence you can just take over it.
> Use the latest source package available in Debian Unstable, package the
> new upstream version and start working on open bugs. Don't forget to
> replace yourself as maintainer in debian/control as you become
> resp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Werner,
On 25.12.2011 15:29, wer...@aloah-from-hell.de wrote:
> So - I'm still interested in working for the policyd weight package but
> currently
> I do not know where to start properly. My idea to repackage the current
> stable one
> wasn't th
Hi Arno,
>> In stable there is still policyd-weight with some open bugs and the current
>> maintainer chris does not have the time to take care about this package any
>> more. With my uploaded package I - principially - wanted to close bug
>> #641227 So my question is: should I go on further with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Werner,
On 25.12.2011 12:48, wer...@aloah-from-hell.de wrote:
> In stable there is still policyd-weight with some open bugs and the current
> maintainer chris does not have the time to take care about this package any
> more. With my uploaded packa
Hello Arno,
thanks for your response.
> * I am not sure what you actually want to achieve? It seems you're
> trying to NMU policyd-weight 0.1.15.1-2 but we have 0.1.15.1-3 already
> in Testing for 8 months. Please make your changes on the latest version
> of the package. That also fixes many out
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Werner,
On 22.12.2011 14:50, wer...@aloah-from-hell.de wrote:
> I am looking for a sponsor for my package "policyd-weight".
>
> * Package name: policyd-weight
>Version : 0.1.15.1-2.1
>Upstream Author : Robert Felber
> * U
83 matches
Mail list logo
