Did not hear anything, so I assume you are busy but would like to see
the current git content in Debian, so I ran 'gbp dch', cleaned up the
changelog and uploaded the result. I applied this diff before the
upload.
diff --git a/debian/changelog b/debian/changelog
index a9efea7..325b31b 100644
Btw, the upstream/1.1.3 tag seem to be missing from your git repository.
--
Happy hacking
Petter Reinholdtsen
Very good to hear from you. :)
[Frank lin Piat]
> What about collab-maint ?
Works for me. But it is a decision I believe is best left to the
package maintainer, so it is up to you. :)
> There are a few more lintian info/warning to fix. I would fix later.
> I: scap-workbench source:
Hello,
On Thu, 2016-12-15 at 15:28 +0100, Petter Reinholdtsen wrote:
> Frank, do you plan to set up a shared git repo for the package now?
What about collab-maint ?
> The build failed everywhere, probably because of missing build
> dependencies, see
>
Wow, that was quick. The package is in Debian now. Frank, do you plan
to set up a shared git repo for the package now? The build failed
everywhere, probably because of missing build dependencies, see
https://buildd.debian.org/status/package.php?p=scap-workbench >.
--
Happy hacking
Petter
[Klee Dienes]
> I dropped the ball due to other distractions.
>
> I'm still interested in collaborating on good SCAP support for Debian,
> but would gladly defer to Petter as sponsor.
>
> I'm not familiar with a SCAP-specific IRC channel. I'll make an effort
> to be on #debian-security when
I dropped the ball due to other distractions.
I'm still interested in collaborating on good SCAP support for Debian,
but would gladly defer to Petter as sponsor.
I'm not familiar with a SCAP-specific IRC channel. I'll make an effort
to be on #debian-security when practical.
I did a test build in unstable using the code from
git://anonscm.debian.org/users/franklin-guest/scap-workbench.git and litian
discovered these issues:
W: scap-workbench source: ambiguous-paragraph-in-dep5-copyright paragraph at
line 22
W: scap-workbench source:
[Petter Reinholdtsen]
> Is there a IRC channel where the SCAP tools in Debian are coordinated?
Perhaps we can meet on #debian-security as a start? I notice Pierre and I
are there already. What about the rest of you?
--
Happy hacking
Petter Reinholdtsen
Hi.
What came out of the plans to upload scap-workbench? Everything seemed to be
lined
up for an upload and then nothing happend.
Is there a IRC channel where the SCAP tools in Debian are coordinated?
I've been making some ad-hoc tools for comparing the CVE security tracker
in debian with the
[Sorry for the late response]
On mar., 2016-05-03 at 22:59 -0400, Greg Elin wrote:
> What is the difference between the collab-maint repo and the Alioth
> group?
An Alioth project is meant for a group of people to collaborate. Each
project has one or more repository (GIT/SVN/HG...), mailing
Franklin,
What is the difference between the collab-maint repo and the Alioth group?
I am new to the maintainer world, but would love to understand more...
Greg Elin
Founder, GovReady PBC
m: 917-304-3488
e: grege...@govready.com
Greg Elin
CEO, GovReady PBC
p: 917-304-3488
e:
[CC'ing Pierre]
On sam., 2016-04-30 at 11:52 -0400, Klee Dienes wrote:
> I'd be happy to sponsor the package. I noticed you have Pierre
> Chifflier listed in the Uploaders: field ... is
> he already sponsoring the package? If so I'll gladly defer.
Your offer is welcome and
On Sat, Apr 30, 2016 at 10:04 PM, Greg Elin wrote:
> Hey Klee!
>
> Thanks for the author of sponsorship! It would be great having your help.
>
> I need to defer to Martin on specifics, as he was doing the initial
> coordination with Pierre. We did the work in 2015 to help
On Sat, Apr 30, 2016 at 11:52 AM, Klee Dienes wrote:
> Thanks for your work in packaging this!
>
> I'd be happy to sponsor the package. I noticed you have Pierre
> Chifflier listed in the Uploaders: field ... is
> he already sponsoring the package? If so
Hey Klee!
Thanks for the author of sponsorship! It would be great having your help.
I need to defer to Martin on specifics, as he was doing the initial
coordination with Pierre. We did the work in 2015 to help push OpenSCAP
toward wider audience. Since OpenSCAP moved to GitHub in late 2014,
Thanks for your work in packaging this!
I'd be happy to sponsor the package. I noticed you have Pierre
Chifflier listed in the Uploaders: field ... is
he already sponsoring the package? If so I'll gladly defer.
I took a quick look and came up with a few minor nits:
--
17 matches
Mail list logo