** Changed in: debian
Status: New => Fix Released
--
[needs-packaging] libcgroup
https://bugs.launchpad.net/bugs/268714
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
Confirmed. 'dpkg --license' shows the license for dpkg (the debian
package manager) itself, not for packages installed on the system. To
verify the copyright of libcgroup, if you have the source you can look
into debian/copyright, or if you have the package installed on your
system you can look int
Hi, Jon, Others
Could someone confirm the license change. I like the split of the
packages, we would like the work to LGPL'ed, dpkg --license shows GPL.
Am I missing something?
Balbir Singh.
--
[needs-packaging] libcgroup
https://bugs.launchpad.net/bugs/268714
You received this bug notification
http://packages.ubuntu.com/source/karmic/libcgroup
** Changed in: ubuntu
Status: Confirmed => Fix Released
--
[needs-packaging] libcgroup
https://bugs.launchpad.net/bugs/268714
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Branch linked: lp:ubuntu/karmic/libcgroup
--
[needs-packaging] libcgroup
https://bugs.launchpad.net/bugs/268714
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ub
Yes, I will revisit this in the next day or so and get this all
straightened out.
--
[needs-packaging] libcgroup
https://bugs.launchpad.net/bugs/268714
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
Hi, Jon,
We need to change the licensing of parse.[ch] to LGPL (the copyright
says that we can distribute the generated files under a different
license if it is a part of a larger program) and we prefer LGPL. Could
you please change the copyright to reflect that. In the case of
pam_cgroup, I need
Ok, I'm now clear on the licensing after discussing [1] with Dhaval.
[1]: http://pastebin.ubuntu.com/259851/
--
[needs-packaging] libcgroup
https://bugs.launchpad.net/bugs/268714
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
All of the source files are licensed under the LGPL (2.1) with 3
exceptions: src/parse.c, src/parse.h, and src/pam/pam_cgroup.c
Those files have licenses in the comment header, parse.[ch] specifies
GPL and pam_cgroup.c specifies BSD-3 (or GPL)
The discussion on REVU revolves around properly docum
Thanks, Jon,
I saw some review comments there, In the beginning I had mentioned the
license as LGPL, I wonder why it is being interpreted as GPL or am I
missing something?
--
[needs-packaging] libcgroup
https://bugs.launchpad.net/bugs/268714
You received this bug notification because you are a m
Package is in REVU: http://revu.ubuntuwire.com/p/libcgroup
--
[needs-packaging] libcgroup
https://bugs.launchpad.net/bugs/268714
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
I've just finished the last changes to the initscripts and the package
is now complete. I'll upload to REVU in the morning and work on getting
it reviewed and advocated. I'll post the REVU link here when the upload
is complete.
--
[needs-packaging] libcgroup
https://bugs.launchpad.net/bugs/268714
Hey guys-
What's the packaging status on this? Feature Freeze is this week, so
if the package is going to make it into Karmic, it needs to get
uploaded ASAP.
Have you posted the package to revu.ubuntuwire.com yet? If not, I
recommend doing so very soon, getting some feedback, and ideally an
adv
Hi, Jon,
Could you post your changes to libcg mailing list. libcg-
de...@lists.sourceforge.net. We'll review and make the changes needed
and also put a longer term TODO to fix RPATH correctly
Thanks,
--
[needs-packaging] libcgroup
https://bugs.launchpad.net/bugs/268714
You received this bug not
Hi, Jon
Thanks for all your effort with the entire packaging, I've been starved
for bandwidth due to various reasons. I'll take a TODO to fix the rpath
issue in the library and work on it. Thanks again!
--
[needs-packaging] libcgroup
https://bugs.launchpad.net/bugs/268714
You received this bug n
Hey Balbir, quick update:
I've added chrpath to my build routine to strip the RPATH from all the
ELF files. So at this point, I've got everything I need to complete the
package (assuming I get enough free time this week ;) ) A more proper
RPATH solution would probably be good, but it's not necessa
Thanks, I'll take a look. I was in the process of figuring out how to
remove rpath, chrpath looks like a good solution, but I wanted to change
automake and libtool to do the right thing.
--
[needs-packaging] libcgroup
https://bugs.launchpad.net/bugs/268714
You received this bug notification becau
Attached is a diff that will fix the manpage warnings for the existing
manpages. I don't have a Fedora box to test on, but I suspect these
changes will work across the board. If the tests look good it would be
cool to get this into the next upstream release.
** Attachment added: "manpage-warning-f
No problem Balbir, I apologize, I did not mean to suggest you were
holding me up, just wondering what the next steps where and how I can
help. I shall beging working on the initscripts and manpage issues. I've
used chrpath before and I believe (but not positive) that it only allows
you to change a
Sorry for holding you up Jon, I was in the process of getting debian up
and running so that I could try the same build scripts on my machine,
but alas migration is very hard. I am trying to setup a virtual machine
for it. Thanks for the offer to write lsb compliant scripts, I think
that would reall
Yes, you are right we need to change that to /etc/default on
debian/ubuntu, we could change the script for debian. What that means
for us upstream is the need to have distro specific changes to the
scripts. I'll see how to best handle that.
I'd be happy to help resolve any issues. We'll remove the
Also, in the release tarballs it's probably a good idea to not include
config.sub, config.guess, and dist/libcgroup.spec since they're all
autogenerated at build-time.
--
[needs-packaging] libcgroup
https://bugs.launchpad.net/bugs/268714
You received this bug notification because you are a member
And here's the extended lintian summary with explainations
** Attachment added: "libcgroup_0.34-1_amd64.lintian-extended"
http://launchpadlibrarian.net/29167577/libcgroup_0.34-1_amd64.lintian-extended
--
[needs-packaging] libcgroup
https://bugs.launchpad.net/bugs/268714
You received this bug
Here's the lintian summary
** Attachment added: "libcgroup_0.34-1_amd64.lintian-summary"
http://launchpadlibrarian.net/29167573/libcgroup_0.34-1_amd64.lintian-summary
--
[needs-packaging] libcgroup
https://bugs.launchpad.net/bugs/268714
You received this bug notification because you are a mem
Ok, I've nearly got it. Here's the only show-stopper issue I've found:
The cgred initscript looks for /etc/sysconfig/cgred.conf. The
sysconfig directory is not standard in Debian/Ubuntu as far as I know,
so we'll need to either provide our own initscript or make the location
of cgred.conf conf
OK, I am uploading what I have for debian packaging as a tarball (done
as a part of libcgroup FOSS.IN workout). The man pages are missing and
this was done for old code, please review/update. I'll help out, feel
free to use this forum or any other to help drive this to completion.
Thanks,
Balbir
** Changed in: debian
Status: Unknown => New
--
[needs-packaging] libcgroup
https://bugs.launchpad.net/bugs/268714
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
** Bug watch added: Debian Bug tracker #536167
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536167
** Also affects: debian via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536167
Importance: Unknown
Status: Unknown
--
[needs-packaging] libcgroup
https://bugs.launchpad.net
** Changed in: ubuntu
Assignee: Dustin Kirkland (kirkland) => Jon Bernard (jbernard)
--
[needs-packaging] libcgroup
https://bugs.launchpad.net/bugs/268714
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hello Balbir, I'm interesting in getting this packaged up for Karmic (if
possible). I'm very interested to see what work you've already completed
and hopefully collaborate on the packaging completion. Can you post your
current work somewhere public? I'll be happy to fixup any issues still
remaining
I was hoping to get this packaged in Jaunty, but we could not. I have
some initial work done for packaging for Ubuntu, should I find the right
forum and post it. I'll probably need help and guidance.
Balbir
--
[needs-packaging] libcgroup
https://bugs.launchpad.net/bugs/268714
You received this b
I know it is sort of late for Intrepid, but it would be a nice feature
to have given that we've enabled cgroups and a bunch of other
controllers. One way would be to add it to Jaunty and backport it? I
don't know if that is acceptable. I would really like to make libcgroup
available to Ubuntu Intre
I've declined this for Intrepid, but assigned to myself. I'll try to
get this packaged when the Jaunty archive opens.
:-Dustin
** Changed in: ubuntu
Assignee: (unassigned) => Dustin Kirkland (kirkland)
--
[needs-packaging] libcgroup
https://bugs.launchpad.net/bugs/268714
You received this
Sorry for the confusion Balbir, my comment was directed at IanW
--
[needs-packaging] libcgroup
https://bugs.launchpad.net/bugs/268714
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
I am not sure which individual(s) to subscribe to this report. I tried
asking on the #ubuntu-kernel. I'll try again.
--
[needs-packaging] libcgroup
https://bugs.launchpad.net/bugs/268714
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: ubuntu
Importance: Wishlist => Undecided
Status: New => Confirmed
** Changed in: ubuntu
Importance: Undecided => Wishlist
--
[needs-packaging] libcgroup
https://bugs.launchpad.net/bugs/268714
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: ubuntu
Importance: Undecided => Wishlist
--
[needs-packaging] libcgroup
https://bugs.launchpad.net/bugs/268714
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
IanW - I think you're confusing "control groups" (libcg) with the CG
language (for programming graphics), so I'm closing the nvidia-common
task.
And adding bug tasks isn't normally the way to get feedback from a
particular developer or group of developers. For that, you should
subscribe the indivi
This is a package request for libcg, which seems to be included already with
nvidia-cg-toolkit.
Adding NVIDIA-Common in case they have any comments or input.
** Also affects: nvidia-common
Importance: Undecided
Status: New
--
[needs-packaging] libcgroup
https://bugs.launchpad.net/bugs
39 matches
Mail list logo
