Upstream tag: barry-0.18.3-2
Upstream diff: git log -p barry-0.18.3..barry-0.18.3-2
Release URL:
http://sourceforge.net/projects/barry/files/barry/barry-0.18.3/sources/debian/barry_0.18.3-2.dsc
Uploaded to sid, thanks!
--
To UNSUBSCRIBE, email to
On Sun, Jun 03, 2012 at 10:34:04AM +0200, intrigeri wrote:
Sure. However, the URLs you provided me until now did not. Did I miss
a way to get the real download URL from the click-one, without firing
up a web browser?
I didn't understand how the .dsc file could be used until I started playing
Hi,
Chris Frey wrote (31 May 2012 22:39:54 GMT) :
Making every maintainer update their package in order to support
hardening seems like the long way around. But so be it. :-)
I agree but the decision was not made this way, so let's deal with
it :)
There is no guarantee either that the diffs
Thanks for your considerate replies, and continued patience.
So far, when I think I can see the end, it is not the end, and
it gets a little frustrating. :-) So your patience is appreciated.
I've done some testing and experiments, and below are my results.
On Tue, May 29, 2012 at 02:46:32PM
Hi Chris,
Chris Frey wrote (26 May 2012 02:15:12 GMT) :
New version available, when you have time:
Looks better and better. I trust we'll manage to get this ready in
time for Wheezy!
I left the hardening checks as-is for now, not overriding them,
since from the conversation on some of the
On Tue, May 29, 2012 at 10:48:43AM +0200, intrigeri wrote:
Commit 85a9d87f makes debian/rules stop passing
DEB_BUILD_MAINT_OPTIONS = hardening=+all to dpkg-buildflags.
I was doing testing with and without the revert, and the lintian
tests did not improve. I plan to do a few more tests though.
Hi,
Chris Frey wrote (29 May 2012 09:45:15 GMT) :
On Tue, May 29, 2012 at 10:48:43AM +0200, intrigeri wrote:
Commit 85a9d87f makes debian/rules stop passing
DEB_BUILD_MAINT_OPTIONS = hardening=+all to dpkg-buildflags.
I was doing testing with and without the revert, and the lintian
tests
On Wed, May 16, 2012 at 12:32:01PM +0200, intrigeri wrote:
So, here's what Lintian tells me this time:
* The no-symbols-control-file Lintian overrides were not updated.
* The new hardening checks detect possible problems: I'll let you
check, override false positives, and fix real problems.
Hi,
Chris Frey wrote (14 May 2012 21:35:45 GMT) :
Development continues on Barry, and I assume it is ok to upload to
Debian as soon as any new version is available.
Yes.
In short:
Uploading to Debian unstable: sure.
Uploading to stable backports once the package reaches the testing
suite:
Hi,
Chris Frey wrote (16 May 2012 03:12:54 GMT) :
Ok, version 0.18.2 is here:
Pretty please, run the latest Lintian (== from Debian sid) with all
nitpicking options enabled *yourself* on the source and binary
packages before pushing them to me. My last review rounds have
basically boiled down
On Mon, May 14, 2012 at 07:48:04PM -0400, Chris Frey wrote:
Hold the presses. I found one more issue. The pkg-config files need to
be renamed to match the major version number (libbarry-18.pc instead of
libbarry-0.pc).
I'll be releasing 0.18.2 to fix this.
Ok, version 0.18.2 is here:
On Sat, May 12, 2012 at 10:38:23AM +0200, intrigeri wrote:
The trailing : is wrong in:
Files: src/vformat.h src/vformat.c:
Oops, thanks.
I also get:
W: barry source: debhelper-but-no-misc-depends barrybackup-gui-dbg
W: barry source: debhelper-but-no-misc-depends libbarry18
W:
On Mon, May 14, 2012 at 05:35:45PM -0400, Chris Frey wrote:
My lintian command didn't catch the *.dsc files. Fixed that, and fixed
all the above.
Hopefully this is the one. :-)
You can grab it in the usual place:
Hi,
Great changes and explanations. See bellow for a few inline replies.
Chris Frey wrote (12 May 2012 00:53:12 GMT) :
2. I don't think src/vformat.{h,c} is supported syntax in a Files:
field in debian/copyright.
Probably not, according to the spec. I changed it to list both files
Hi,
Chris Frey wrote (08 May 2012 06:01:58 GMT) :
I believe this release can be uploaded.
Almost :)
Next review round results in:
1. debian/copyright may be syntaxically correct, but it looks weird
compared to how people usually put things in there.
Attached patch fixes this. Please
intrigeri wrote (11 May 2012 08:23:58 GMT) :
Next review round results in:
Also, Lintian in --info --display-info --pedantic mode still outputs
a bunch of relevant comments.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On Fri, May 11, 2012, intrigeri wrote:
Next review round results in:
Thanks :-)
1. debian/copyright may be syntaxically correct, but it looks weird
compared to how people usually put things in there.
Attached patch fixes this. Please consider applying it.
I applied the patch, with a
On Mon, Apr 30, 2012 at 01:46:13PM +0200, intrigeri wrote:
$ sudo apt-get install libconfig-model-perl
$ cme check dpkg-copyright
$ cme dump dpkg-copyright
Thanks intrigeri. The cme check did find a syntax oddity, although
the error message it produced was a bit cryptic. :-)
I believe this
Hi,
Chris Frey wrote (08 May 2012 06:01:58 GMT) :
I believe this release can be uploaded.
I'll review this package later this week, probably on Friday.
I'm assuming that you will do the actual upload?
I will, once I'm happy with the state of the package.
--
To UNSUBSCRIBE, email to
On Tue, May 08, 2012 at 11:22:48AM +0200, intrigeri wrote:
I'm assuming that you will do the actual upload?
I will, once I'm happy with the state of the package.
Excellent. Thanks very much. Let me know if you find any
show stoppers. :-)
- Chris
--
To UNSUBSCRIBE, email to
Chris Frey wrote (30 Apr 2012 00:49:23 GMT) :
Is there a tool I can use to make sure I've got the new format right?
I ran it against lintian on sid, but I'm not sure if that's enough.
$ sudo apt-get install libconfig-model-perl
$ cme check dpkg-copyright
$ cme dump dpkg-copyright
(See also
On Fri, Apr 27, 2012 at 01:38:29AM +0200, intrigeri wrote:
Looks like great work. Congrats!
Thanks for the feedback!
* can you please convert debian/copyright to DEP5 format?
(you're almost there, see http://dep.debian.net/deps/dep5/)
Is there a tool I can use to make sure I've got the
Chris Frey wrote (25 Apr 2012 23:59:02 GMT) :
The latest git sources from http://repo.or.cz/w/barry.git should
compile on sid, with no lintian warnings. Please let me know what
you think.
Looks like great work. Congrats!
I've not built the package yet. A quick review only reveals:
* what's
Hi Chris,
intrigeri wrote (26 Apr 2012 23:38:29 GMT) :
Chris Frey wrote (25 Apr 2012 23:59:02 GMT) :
The latest git sources from http://repo.or.cz/w/barry.git should
compile on sid,
I concur.
with no lintian warnings.
I see two kinds of warnings: debhelper-but-no-misc-depends and
On Thu, Apr 26, 2012 at 03:36:45PM +0200, intrigeri wrote:
The latest git sources from http://repo.or.cz/w/barry.git should
compile on sid, with no lintian warnings. Please let me know what
you think.
Where can I find the corresponding orig.tar.gz?
I'm hoping to release a real 0.18.0
Hi Chris,
Chris Frey wrote (25 Apr 2012 23:59:02 GMT) :
I'm hoping you're still interested in reviewing Barry for upload to
Debian sid.
Sure.
As for Barry itself, there's only general documentation updates, and
one feature in the Desktop GUI that needs to be implemented before
version 0.18
Hi intrigeri,
I'm hoping you're still interested in reviewing Barry for upload to
Debian sid.
As for Barry itself, there's only general documentation updates, and one
feature in the Desktop GUI that needs to be implemented before version 0.18
is released.
As for the Debian packaging, it is
Hi,
Without opensync plugins, though, we should leave the Desktop out
of Debian for now. Is there an easy way to make packages optional?
There is, actually, a way to make your debian/control dynamic:
http://lists.debian.org/msgid-search/87y5rcla88.fsf@algernon.balabit
Cheers,
--
intrigeri
On Mon, Mar 19, 2012 at 06:53:19PM +0100, intrigeri wrote:
Hi,
Without opensync plugins, though, we should leave the Desktop out
of Debian for now. Is there an easy way to make packages optional?
There is, actually, a way to make your debian/control dynamic:
Hi,
Chris Frey wrote (03 Mar 2012 14:50:14 GMT) :
Stable is what I had handy. I realize this is a work in progress.
I suggest you use a pbuilder sid chroot to build packages
that are supposed to be uploaded into sid at some point.
There's a large body of work on the opensync side that is not
Hi,
Chris Frey wrote (04 Mar 2012 13:59:49 GMT) :
I, as the one who's spending time to review your packaging, and
offered to sponsor your packages, do care. I find it useful to be
able to infer, from a given package version number (be it a source
or binary package built from your Git
On Sun, Mar 04, 2012 at 01:33:14PM +0100, intrigeri wrote:
I named it opensync0 since that plugin depends on libopensync0, which
is available in Squeeze.
libopensync0 was a binary library package built from the opensync
source package. Using ABI numbers in such a binary package name is
On Thu, Mar 01, 2012 at 09:26:34AM +0100, intrigeri wrote:
The answer is basically none. Once can maintain a package in Debian
(as is: doing maintenance work, being responsible, and being in the
Maintainer: control field) without any kind of special status.
Excellent!
In the latest Barry
Hi,
Chris Frey wrote (03 Mar 2012 08:27:32 GMT) :
In the latest Barry git tree, I've updated the debian packaging to
Standards-Version 3.9.1 (the latest for Squeeze)
We don't wait until all previous Debian releases are EOL'd before we
start following the latest Debian Policy. Please follow the
On Sat, Mar 03, 2012 at 02:54:34PM +0100, intrigeri wrote:
We don't wait until all previous Debian releases are EOL'd before we
start following the latest Debian Policy. Please follow the latest
available Standards-Version: Debian Policy 3.9.3 was released.
See
Hi,
Chris Frey wrote (01 Mar 2012 01:59:39 GMT) :
How much lag time is there between applying for maintainer status,
and being able to have sponsored uploads?
The answer is basically none. Once can maintain a package in Debian
(as is: doing maintenance work, being responsible, and being in
Hi Chris!
One month has passed, and nobody adopted the barry package in Debian;
the Wheezy freeze will happen in a few months. I suggest you decide
whether you want to take care of barry in Debian, so that we avoid
uploading packages in a hurry at the last minute.
My help proposal (reviews and
On Thu, Mar 01, 2012 at 01:37:42AM +0100, intrigeri wrote:
Hi Chris!
One month has passed, and nobody adopted the barry package in Debian;
the Wheezy freeze will happen in a few months. I suggest you decide
whether you want to take care of barry in Debian, so that we avoid
uploading
Hi,
Chris Frey wrote (27 Jan 2012 02:58:23 GMT) :
Changelog:
The changelog needs to be kept up to date in Debian. I've
tried to limit myself to just using my own entry at the top,
but I'm willing to find a better way to share that file if
downstream wants to work with
On Fri, Jan 27, 2012 at 10:20:10AM +0100, intrigeri wrote:
I don't understand very well what you are expecting from the
Debian maintainer. Be them anyone else or (soon?) yoursef, what they
must put in debian/changelog is:
Oh, I know the changelog must be updated, but some maintainers have
the
Hi Chris,
Chris Frey wrote (24 Jan 2012 01:04:48 GMT) :
1) Version 0.18 is nearing readiness
I'm hoping to release 0.18, maybe mid-Feb. There's a GUI in
development to make syncing with opensync easier as well.
It would be nice to have this coordinated with
Debian
On Thu, Jan 26, 2012 at 02:04:42AM +0100, intrigeri wrote:
Changelog:
The changelog needs to be kept up to date in Debian. I've
tried to limit myself to just using my own entry at the top,
but I'm willing to find a better way to share that file if
downstream wants
42 matches
Mail list logo
