Bug#870621: RFS: deepin-gettext-tools/1.0.6+git20170731-1 [ITP]
Hi, I have a quick look of this package, this is my comment: * d/compat should be 10 * please ask upstrem to add license header to desktop_ts_convert.pl and policy_ts_convert.py * please fix binary-without-manpage lintian warning. Thanks, -- Liang Guo http://guoliang.me/
Bug#869898: RFS: dtkcore/0.3.3-1 [ITP]
On Thu, Aug 3, 2017 at 5:19 PM, Boyuan Yang <073p...@gmail.com> wrote: > According to my understanding [1], this should be a recommendation and not a > requirement for using (L)GPL licenses. > > Anyway I prepared a new snapshot for dtkcore with upstream fixes: > > * https://anonscm.debian.org/git/pkg-deepin/dtkcore.git > * https://mentors.debian.net/package/dtkcore > > I am still working with upstream to track their changes. Maybe we should push > an initial version into Debian archive first. > > [1] https://www.gnu.org/licenses/gpl-faq.html#NoticeInSourceFile > > Regards, > Boyuan Yang Uploaded, Thank you for your work on Debian. For it is a new package in Debian, it needs a little more time for ftp-master team . to check it. Thanks, -- Liang Guo http://guoliang.me/
Bug#869898: RFS: dtkcore/0.3.3-1 [ITP]
On Mon, Jul 31, 2017 at 1:13 PM, Boyuan Yang <073p...@gmail.com> wrote: >>> >>> Meanwhile, source packages on debomatic-amd64, mentors.d.o and Git >>> repository >>> has been updated already to fix problems of non-existent pkg-deepin team >>> (See >>> #868544). I believe the source package should be ready for an upload. >> Cannot you cate pkg-deepin team in alioth? It's a good idea to >> maintain package by >> team. > > Unfortunately not at this time. I asked on #alioth yesterday but no > one stepped out to deal with the team creation request. formorer said > it is not his part of job and I don't know who is going to take care > of related works. > I have created project pkg-deepin on alioth, pease join in https://alioth.debian.org/projects/pkg-deepin/ -- Liang Guo
Bug#869898: RFS: dtkcore/0.3.3-1 [ITP]
On Mon, Jul 31, 2017 at 10:17 AM, Boyuan Yang <073p...@gmail.com> wrote: > > Sure. I have reminded them of this issue. I will update debian/copyright file > as soon as new upstream version (with fixes) gets released. My opinion is that > this issue shouldn't be a blocker for upload. IMO, upstream should fix this problem BEFORE it can be uploaded to Debian, But I'm not sure if it is madated in Debian, I advice you raise this problem in debian-devel or debian-legel maillist. > > Meanwhile, source packages on debomatic-amd64, mentors.d.o and Git repository > has been updated already to fix problems of non-existent pkg-deepin team (See > #868544). I believe the source package should be ready for an upload. Cannot you cate pkg-deepin team in alioth? It's a good idea to maintain package by team. Thanks, -- Liang Guo
Bug#869898: RFS: dtkcore/0.3.3-1 [ITP]
Have you ask upstream to correct source file's license header ?
Thanks,
On Thu, Jul 27, 2017 at 11:40 PM, Boyuan Yang <073p...@gmail.com> wrote:
> 2017-07-27 22:47 GMT+08:00 Liang Guo :
>> On Thu, Jul 27, 2017 at 10:25 PM, ChangZhuo Chen wrote:
>>> On Thu, Jul 27, 2017 at 09:30:52PM +0800, Boyuan Yang wrote:
>>>> Alioth packaging repository:
>>>>
>>>> https://anonscm.debian.org/git/collab-maint/dtkcore.git
>>>
>>> * The copyrights in src/log/* are different from other files, please
>>> check copyright header of every file and list them in
>>> debian/copyright.
>>>
>>> * This symbol control file for libdtkcore.so is missing. Please help to
>>> add it.
>>
>> Agree, beside these problem, please notice:
>>
>> * debian/docs is empty please remove
>>
>> * Their should be an short license declaration in each *.{c,h,cpp}
>> file. For GPL3 license files, the short license should like this:
>>
>> Copyright (C)
>>
>> This program is free software: you can redistribute it and/or modify
>> it under the terms of the GNU General Public License as published by
>> the Free Software Foundation, either version 3 of the License, or
>> (at your option) any later version.
>>
>> This program is distributed in the hope that it will be useful,
>> but WITHOUT ANY WARRANTY; without even the implied warranty of
>> MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
>> GNU General Public License for more details.
>>
>> You should have received a copy of the GNU General Public License
>> along with this program. If not, see <http://www.gnu.org/licenses/>.
>>
>> Please ask the original author to complete the license declaration.
>>
>> * debian/copyright file should obey DEP-5 proposal[1]
>>
>>
>> [1] https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
>>
>>
>> --
>> Liang Guo
>> http://guoliang.me/
>
> Thank you all for detailed review with this package.
>
> I have checked the packaging src again with check-all-the-things and
> fixed all problems that can be fixed in debian/ directory. d/copyright
> information has been updated after manual check with the source code.
>
> Detailed changes can be found on
> anonscm.debian.org/git/collab-maint/dtkcore.git git repository. Source
> packages on mentors.d.o and debomatic-amd64.d.o are also updated
> accordingly.
>
> Thanks,
> Boyuan Yang
--
Liang Guo
http://guoliang.me/
Bug#869898: RFS: dtkcore/0.3.3-1 [ITP]
On Thu, Jul 27, 2017 at 10:25 PM, ChangZhuo Chen wrote:
> On Thu, Jul 27, 2017 at 09:30:52PM +0800, Boyuan Yang wrote:
>> Alioth packaging repository:
>>
>> https://anonscm.debian.org/git/collab-maint/dtkcore.git
>
> * The copyrights in src/log/* are different from other files, please
> check copyright header of every file and list them in
> debian/copyright.
>
> * This symbol control file for libdtkcore.so is missing. Please help to
> add it.
Agree, beside these problem, please notice:
* debian/docs is empty please remove
* Their should be an short license declaration in each *.{c,h,cpp}
file. For GPL3 license files, the short license should like this:
Copyright (C)
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
Please ask the original author to complete the license declaration.
* debian/copyright file should obey DEP-5 proposal[1]
[1] https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
--
Liang Guo
http://guoliang.me/
Bug#869898: RFS: dtkcore/0.3.3-1 [ITP]
Interesting, I'll have a look On Thu, Jul 27, 2017 at 9:30 PM, Boyuan Yang <073p...@gmail.com> wrote: > Package: sponsorship-requests > Severity: wishlist > X-Debbugs-CC: czc...@debian.org > > Dear mentors, > > I am looking for a sponsor for my package "dtkcore". > > This source package provides a library used by various software from Deepin > Linux. This is the dependency of many Deepin software and DDE (Deepin Desktop > Environment). > > This package is parallel with previous "dtksettings" thus can be uploaded at > the same time without conflicts/dependency problems. > > * Package name: dtkcore > Version : 0.3.3-1 > Upstream Author : Deepin Technology Co., Ltd. > * URL : https://www.deepin.org/ >Section : devel > > It builds those binary packages: > > libdtkcore-dev - Deepin Tool Kit Core Devel library > libdtkcore1 - Deepin Tool Kit Core library > > To access further information about this package, please visit the following > URL: > > https://mentors.debian.net/package/dtkcore > > Alternatively, one can download the package with dget using this command: > > dget -x https://mentors.debian.net/debian/pool/main/d/dtkcore/ > dtkcore_0.3.3-1.dsc > > Alternatively, one can retrieve more information from debomatic-amd64: > > http://debomatic-amd64.debian.net/distribution#unstable/dtkcore/0.3.3-1/ > > Alioth packaging repository: > > https://anonscm.debian.org/git/collab-maint/dtkcore.git > >More information about hello can be obtained from https://github.com/ > linuxdeepin/dtkcore . > > Changes since the last upload: > > dtkcore (0.3.3-1) unstable; urgency=medium > . >* Initial release (Closes: #869894) > > Regards, > Boyuan Yang -- Liang Guo http://guoliang.me/
Bug#800966: RFS: kimchi/1.5.1-1 [ITP] -- HTML5 based management tool for KVM
On Wed, Oct 7, 2015 at 11:39 PM, Frederic Bonnard wrote: > interesting. I tried to build the package on amd64 too but in a schroot env > (unstable) and it built fine. > Could you explain or give some links on how to setup this sbuild env ? > Thanks a lot, Sbuild is simple to setup, please visit its wiki [1][2] to see how to build package with sbuild. Packages accepted by ftp-master are built with sbuild for all architecture and uploaded to debian archive. Beside sbuild, you may use pbuilder[3] to validate package build dependency. [1] https://wiki.debian.org/sbuild [2] https://wiki.ubuntu.com/SimpleSbuild [3] https://www.debian.org/doc/manuals/maint-guide/build.zh-cn.html#pbuilder -- Liang Guo
Bug#800966: RFS: kimchi/1.5.1-1 [ITP] -- HTML5 based management tool for KVM
─┐ │ Summary │ └──────────┘ Build Architecture: amd64 Build-Space: 18896 Build-Time: 213 Distribution: unstable Fail-Stage: build Host Architecture: amd64 Install-Time: 77 Job: /z/src/kimchi/kimchi_1.5.1-1.dsc Machine Architecture: amd64 Package: kimchi Package-Time: 388 Source-Version: 1.5.1-1 Space: 18896 Status: attempted Version: 1.5.1-1 Liang Guo http://guoliang.me/
Bug#737751: RFS: read-edid/3.0.1-1 [ITA]
Uploaded, Thanks, -- Liang Guo http://guoliang.me/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAJwrgW6bRLiczth0=s6_nmkvs9ih48jx2jsy22u-7rxbw3b...@mail.gmail.com
Re: Bug#737390: RFS: kerneltop/0.91-1 [ITA]
On Tue, Feb 4, 2014 at 3:45 PM, Dariusz Dwornikowski wrote: > Hey, > > Thank You very much for your suggestions !! > > Here is a link [1] to the package fixed according to your suggestions. > > [1] https://mentors.debian.net/package/kerneltop > Uploaded. Thanks for your work on Debian. -- Liang Guo http://guoliang.me/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAJwrgW42VNbormXqf_xqfbJuSwTpZRRjdNQ44Hdt35F==wa...@mail.gmail.com
Bug#737390: RFS: kerneltop/0.91-1 [ITA]
Interesting package, this is my review: 1 upstream ships manpage, so please remove debian/kerneltop.1 2 3.0 (quilt) always use quilt to manage patches, so README.source is meaningless, please remove 3 Upstream makefile don't use CFLAGS environmen which includes build harden flags. I advice you pach "CCFLAGS=-g/-s" in makefile with "CCFLAGS=-g/-s $(CFLAGS)" to include build harden flags and remove debian/source/lintian-overrides 4 Please update debian/copyright with DEP5 format[2]. Thanks for your working on debian. [1] https://wiki.debian.org/Hardening [2] http://dep.debian.net/deps/dep5/ -- Liang Guo http://guoliang.me -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cajwrgw6pjtwgixsdc+ax8ii3k1hqjctqazozhtcdboyy_m+...@mail.gmail.com
Bug#736839: RFS: sosreport/3.1-1 ITP
Hi, Adam, On Mon, Jan 27, 2014 at 9:16 PM, Adam Stokes wrote: > Package: sponsorship-requests > > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "sosreport" > > * Package name : sosreport >Version: 3.1-1 >Upstream Author : Adam Stokes > * URL : https://github.com/sosreport/sosreport > * License: GPL-2 >Section : admin > > It builds those binary packages: > > sosreport - Set of tools to gather troubleshooting data from a system > The latest standards version is 3.9.5, please bump to it. Before uploading packages, you'd better use lintian and lintian4py to check them, it can help you to find potential problems in your package. Thanks, -- Liang Guo http://guoliang.me/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cajwrgw7m04fscs6h2cxtfbwc_r0f0re5dzzwdt7ecg_sd_y...@mail.gmail.com
Bug#717931: RFS: sosreport/3.0-1 ITP
On Mon, Jul 29, 2013 at 6:55 AM, gregor herrmann wrote: > On Mon, 29 Jul 2013 05:45:41 +0800, Liang Guo wrote: > > [quoting repaired, please don't top-post + fullquote] > >> On Mon, Jul 29, 2013 at 1:13 AM, Jakub Wilk wrote: > >> > lintian4python emits: > >> Are you using the latest lintian ? > > I'm sure he's using the latest _lintian4python_. > :) > I have not use lintian4python, sorry. Hi, Adam, Would you like fix these problem ? I can upload it once it is ready. Thanks, -- Liang Guo http://bluestone.cublog.cn -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAJwrgW6jOEdSAA2Mu4jxCd5uprXzQX_w+1LKaJVAt=vfi_a...@mail.gmail.com
Bug#717931: RFS: sosreport/3.0-1 ITP
Hi, Jakub Are you using the latest lintian ? Before I upload it to debian, I have check it with lintian, this is the result: P: sosreport: no-upstream-changelog I: sosreport: hyphen-used-as-minus-sign usr/share/man/man1/sosreport.1.gz:6 I: sosreport: hyphen-used-as-minus-sign usr/share/man/man1/sosreport.1.gz:7 I: sosreport: hyphen-used-as-minus-sign usr/share/man/man1/sosreport.1.gz:8 I: sosreport: hyphen-used-as-minus-sign usr/share/man/man1/sosreport.1.gz:9 I: sosreport: hyphen-used-as-minus-sign usr/share/man/man1/sosreport.1.gz:10 I: sosreport: hyphen-used-as-minus-sign usr/share/man/man1/sosreport.1.gz:11 I: sosreport: hyphen-used-as-minus-sign usr/share/man/man1/sosreport.1.gz:12 I: sosreport: hyphen-used-as-minus-sign usr/share/man/man1/sosreport.1.gz:13 I: sosreport: hyphen-used-as-minus-sign usr/share/man/man1/sosreport.1.gz:14 Thanks, Liang On Mon, Jul 29, 2013 at 1:13 AM, Jakub Wilk wrote: > * Adam Stokes , 2013-07-26, 13:07: >> >> http://mentors.debian.net/debian/pool/main/s/sosreport/sosreport_3.0-1.dsc > > > I see the package has been already uploaded, but hey, it's never to late for > a review. ;) > > lintian4python emits: > > w: sosreport source: xs-python-version-instead-of-x-python-version > e: sosreport: pyflakes-undefined-name > usr/share/sosreport/sos/sosreport.py:264: value > e: sosreport: pyflakes-undefined-name > usr/share/sosreport/sos/sosreport.py:293: _options > e: sosreport: pyflakes-undefined-name > usr/share/sosreport/sos/sosreport.py:299: isinsance > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/archive.py:207 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/archive.py:260 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/plugins/__init__.py:609 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/plugins/gluster.py:50 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/plugins/gluster.py:77 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/plugins/nfsserver.py:38 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/plugins/rhui.py:39 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/plugins/s390.py:70 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/policies/__init__.py:294 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/policies/__init__.py:303 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/policies/__init__.py:407 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/policies/__init__.py:422 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/policies/__init__.py:458 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/policies/debian.py:36 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/policies/redhat.py:30 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/policies/redhat.py:78 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/policies/redhat.py:141 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/policies/redhat.py:150 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/policies/ubuntu.py:24 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/policies/windows.py:31 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/sosreport.py:108 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/sosreport.py:810 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/sosreport.py:819 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/sosreport.py:825 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/sosreport.py:915 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/sosreport.py:985 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/utilities.py:59 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/utilities.py:87 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/utilities.py:218 > x: sosreport: except-without-exception-type > usr/share/sosreport/sos/utilities.py:225 > > -- > Jakub Wilk > > > -- > To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: http://lists.debian.org/20130728171300.ga6...@jwilk.net > -- Liang Guo http://bluestone.cublog.cn -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAJwrgW5A3cSawz+VrbyX=eox7snoziymvrxoy6u5humh8_a...@mail.gmail.com
Bug#717931: RFS: sosreport/3.0-1 ITP
Hi, adam, On Sat, Jul 27, 2013 at 1:07 AM, Adam Stokes wrote: > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "sosreport" > > * Package name: sosreport > Version : 3.0-1 > Upstream Author : Adam Stokes > * URL : https://github.com/sosreport/sosreport > * License : GPLv2+ > Section : admin > > It builds those binary packages: > > sosreport - Set of tools to gather troubleshooting data from a system > > To access further information about this package, please visit the following > URL: > > http://mentors.debian.net/package/sosreport > > Alternatively, one can download the package with dget using this command: > > dget -x > http://mentors.debian.net/debian/pool/main/s/sosreport/sosreport_3.0-1.dsc > > More information about hello can be obtained from > https://github.com/sosreport/sosreport > > Changes since the last upload: > > * New upstream release v3.0 > Features include: > - Openstack, MAAS, Juju, and other cloud technologies > - Extended policies to allow for easier cross distribution support > - Cross distribution support for Debian, Ubuntu, Fedora, and >Red Hat Enterprise Linux > - Increase execution speed of plugins > * Fixes traceback error in the utilities log (Closes: #717401) > > Regards, > Adam Stokes > -- Uploaded, Thank you for package sosreport for debian. BTW: do you use upstream git repository to keep your work ? If so, I advice you add VCS-* fields in debian/control. Thanks, -- Liang Guo http://bluestone.cublog.cn -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAJwrgW6hKNtsXz=Nx-mZauZsKXS+WJvaxQ1=DoVhW8du=l5...@mail.gmail.com
Bug#705192: RFS: sosreport/2.3-2 ITP
On Wed, May 8, 2013 at 5:56 PM, Liang Guo wrote: > Hi, Adam, > On Tue, Apr 16, 2013 at 11:03:33AM -0400, Adam Stokes wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> > >> I believe I've fixed all of the above issues and they were committed >> upstream today[1][2]. >> >> dget -x >> http://mentors.debian.net/debian/pool/main/s/sosreport/sosreport_2.3+git20130416-1.dsc >> you use version 2.3+git20130416, which is bigger then version 2.3, so 2.3~git20130416 or 2.2+git20130416 should be better. Thanks, -- Liang Guo http://bluestone.cublog.cn -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cajwrgw6cy7aafwk7jg1gkjjuk3kfqm3xsmntm6orer3fkfg...@mail.gmail.com
Bug#705192: RFS: sosreport/2.3-2 ITP
Hi, Adam, On Tue, Apr 16, 2013 at 11:03:33AM -0400, Adam Stokes wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I believe I've fixed all of the above issues and they were committed > upstream today[1][2]. > > dget -x > http://mentors.debian.net/debian/pool/main/s/sosreport/sosreport_2.3+git20130416-1.dsc > This version looks better then the original one, but there are still some minor glitch should be fixed: 1) lintian information, you should run lintian with '-IE --pedantic', lintian will tell you more if there are any problem. There are still some lintian information, but I don't care of them. you may fix them when you polish your package. 2) You use old format copyright files, it is better to switch to DEP5[1] compatible format. lintian shows this information. 3) The section is python, but I think admin should be better, after all, sosreport is a sysadmin tool 4) Please move LICENSE file to usr/share/doc/sosreport, rather than remove it. [1] http://dep.debian.net/deps/dep5/ You should fix 4) before I can upload it to ftp-master, others are just for advice. Thanks and Regards, -- Liang Guo http://bluestone.cublog.cn signature.asc Description: Digital signature
Bug#705192: RFS: sosreport/2.3+nmu1 ITP
Hi, On Thu, Apr 11, 2013 at 1:13 PM, Adam Stokes wrote: > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "sosreport" > > Package name: sosreport > Version : 2.3+nmu1 > Upstream Author : Bryn Reeves > URL : https://github.com/sosreport/sosreport > License : GPL2+ > Section : python > > It builds those binary packages: > > sosreport - A set of tools to gather troubleshooting > information from a system > > To access further information about this package, > please visit the following URL: > > http://mentors.debian.net/package/sosreport > > > Alternatively, one can download the package > with dget using this command: > > dget -x > http://mentors.debian.net/debian/pool/main/s/sosreport/sosreport_2.3+nmu1.dsc > > More information about sosreport can be obtained from > https://github.com/sosreport. > > Changes since the last upload: > > sosreport (2.3+nmu1) unstable; urgency=low > > * NMU > * Package updated from git rev 1baf743 > > -- Adam Stokes Thu, 11 Apr 2013 00:50:51 -0400 > > Regards, > -- > Adam Stokes > adam.sto...@ubuntu.com > "Don't salt your green beans before you try them, > some may think you make rash decisions." I have a brief review of this package, this is my comment: 1 you are the maintainer, you don't need NMU 2 For it is not in Debian yet, you should use version number 2.3+nmu1, just use 2.3 3 you should not ship pyc in you package 4 binary package should be included 5 please run lintian against *.changes Thanks for your work on sosreport. -- Liang Guo http://bluestone.cublog.cn -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cajwrgw6euaprdl14xfrexyfkivjcbbr-jnmk4yph8ufw6bv...@mail.gmail.com
Re: RFS: flashcache
On Sun, May 27, 2012 at 09:32:14AM +0200, Arno Töll wrote: > Hi, > > On 27.05.2012 08:12, Liang Guo wrote: > > When the new package is ready, I'd like to sponsor your package. > > I have currently no intentions to maintain flashcache anymore and > everyone else interested to pick it up may do so. The package was ready > to use in November, so updating it to a newer version shouldn't be much > of a deal. See RFP #635504 for details and [1] for the corresponding > repository. > > If you care enough, you can just pick it up yourself. I do not need a > sponsor anymore by the way. Well, I'll take over. Do you still use it ? Thanks and Regards, -- Liang Guo http://bluestone.cublog.cn signature.asc Description: Digital signature
Re: RFS: flashcache
Hi, Arno, On Thu, Nov 24, 2011 at 01:03:06AM +0100, Arno T鰈l wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Dear mentors, > > I am looking for a sponsor for my package "flashcache". > > * Package name: flashcache >Version : 1.0+git201109221219-1 >Upstream Author : Mohan Srinivasan et. al. (for Facebook) > * URL : https://github.com/facebook/flashcache > * License : GPL-2 / BSD-2-clause >Section : kernel > > It builds those binary packages: > > flashcache-dkms - write-back block device cache for Linux (DKMS version) > flashcache-utils - write-back block device cache for Linux (user space > utilities) > > To access further information about this package, please visit the > following URL: > > http://mentors.debian.net/package/flashcache > > Alternatively, one can download the package with dget using this command: > > dget -x > http://mentors.debian.net/debian/pool/main/f/flashcache/flashcache_1.0+git201109221219-1.dsc > it's a long time since you prepare this package, and there are many changes in upstream, would you like sync your package with upstream ? When the new package is ready, I'd like to sponsor your package. Thanks and Regards, -- Liang Guo http://bluestone.cublog.cn signature.asc Description: Digital signature
RFS: spice-protocol (0.8.2-1)
Dear mentors, I am looking for a sponsor for the new version 0.8.2-1 of my package "spice-protocol". It builds these binary packages: libspice-protocol-dev - SPICE protocol headers The package appears to be lintian clean. The package can be found on mentors.debian.net: dget -x http://mentors.debian.net/debian/pool/main/s/spice-protocol/spice-protocol_0.8.2-1.dsc I would be glad if someone uploaded this package for me. Thanks and Regards, -- Liang Guo http://bluestone.cublog.cn signature.asc Description: Digital signature
RFS: spice-vdagent (2nd try)
Dear mentors, I am looking for a sponsor for my package "spice-vdagent". * Package name: spice-vdagent Version : 0.8.1-1 Upstream Author : Gerd Hoffmann * URL : http://www.spice-space.org/ * License : GPL-3+ Section : x11 It builds those binary packages: spice-vdagent - Spice agent for Linux To access further information about this package, please visit the following URL: http://mentors.debian.net/package/spice-vdagent Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/s/spice-vdagent/spice-vdagent_0.8.1-1.dsc I would be glad if someone uploaded this package for me. Thanks and Regards, -- Liang Guo http://bluestone.cublog.cn signature.asc Description: Digital signature
Re: dput failure to mentors.debian.net
On Mon, Oct 10, 2011 at 5:53 PM, Arno Töll wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hello Paul, > > On 10.10.2011 09:26, Paul Elliott wrote: >> Because of previous difficulty dput'ing swe-standard-data with http >> I decided to upload it with ftp. Here is the console output: As you can see >> in >> succeeds. > > you should have gotten this email: > > > 01:10:08,161 ERROR [debexpo.importer.3192] Rejected: You are not > uploading to one of those Debian distributions: oldstable stable > unstable experimental stable-backports oldstable-backports > oldstable-backports-sloppy stable-security testing-security > stable-proposed-updates testing-proposed-updates sid wheezy squeeze > lenny squeeze-backports lenny-backports lenny-security > lenny-backports-sloppy lenny-volatile squeeze-security squeeze-updates > wheezy-security > Looks like experimental is not included, can it be included ? Thanks, -- Liang Guo http://bluestone.cublog.cn -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cajwrgw6woqthjt0evcgu7kav6jclmc79z9owpwetzkengsx...@mail.gmail.com
RFS: spice-vdagent
Dear mentors, I am looking for a sponsor for my package "spice-vdagent". * Package name: spice-vdagent Version : 0.8.1-1 Upstream Author : Gerd Hoffmann * URL : http://www.spice-space.org/ * License : GPL-3+ Section : x11 It builds those binary packages: spice-vdagent - Spice agent for Linux To access further information about this package, please visit the following URL: http://mentors.debian.net/package/spice-vdagent Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/s/spice-vdagent/spice-vdagent_0.8.1-1.dsc I would be glad if someone uploaded this package for me. Thanks and Regards, -- Liang Guo http://bluestone.cublog.cn signature.asc Description: Digital signature
RFS: spice-gtk
Dear mentors, I am looking for a sponsor for my package "spice-gtk". * Package name: spice-gtk Version : 0.7-1 Upstream Author : Gerd Hoffmann , Marc-André Lureau * URL : http://www.spice-space.org/ * License : LGPL 2.1+ Section : misc To access further information about this package, please visit the following URL: http://mentors.debian.net/package/spice-gtk Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/s/spice-gtk/spice-gtk_0.7-1.dsc I would be glad if someone uploaded this package for me. Thanks and Regards, -- Liang Guo http://bluestone.cublog.cn signature.asc Description: Digital signature
RFS: herculesstudio (updated package)
Dear mentors, I am looking for a sponsor for the new version 1.3.0-1 of my package "herculesstudio". It builds these binary packages: herculesstudio - Hercules GUI front-end The package appears to be lintian clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/h/herculesstudio - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/h/herculesstudio/herculesstudio_1.3.0-1.dsc I would be glad if someone uploaded this package for me. Thanks and Regards, -- Liang Guo http://bluestone.cublog.cn signature.asc Description: Digital signature
Re: RFS: spice
On Sun, Jul 24, 2011 at 5:50 PM, Jakub Wilk wrote:
> * Liang Guo , 2011-07-24, 12:24:
>>>>
>>>> I override configure-generated-file-in-source lintian warnings, for
>>>> spice_0.8.2.orig-celt.tar.gz come with config.log and config.status and
>>>> debian/rules will delete them.
>>>> - dget
>>>> http://mentors.debian.net/debian/pool/main/s/spice/spice_0.8.2-1.dsc
>>>
>>> You shouldn't need to override these warnings if the clean target would
>>> just seriously delete them (not as make distclean but plain rm -f).
>>> Alternatively you could stuff them into debian/clean. That should get rid of
>>> the warning and thus the need to override.
>>
>> The lintian warning configure-generated-file-in-source is caused by
>> upstream celt package, it comes with config.log and config.status, to remove
>> this lintian warning, I need repack spice_0.8.2.orig-celt.tar.gz which I
>> think it is not nessary.
>
> That's right. This is what lintian-info says:
>
> N: configure-generated-file-in-source
> N:
> N: Leaving config.cache/status causes autobuilders problems. config.cache
> N: and config.status are produced by GNU autoconf's configure scripts. If
> N: they are left in the source package, autobuilders may pick up settings
> N: for the wrong architecture.
> N: N: The clean rule in debian/rules should remove this file. This
> should
> N: ideally be done by fixing the upstream build system to do it when you
> N: run the appropriate cleaning command (and don't forget to forward the
> N: fix to the upstream authors so it doesn't happen in the next release).
> N: If that is already implemented, then make sure you are indeed cleaning
> N: it in the clean rule. If all else fails, a simple rm -f should work.
> N: N: Note that Lintian cannot reliably detect the removal in the clean
> N: rule, so once you fix this, please ignore or override this warning.
>
> However, lintian info is wrong in one aspect: clean target is not the
> correct place to remove these files. The purpose of the clean target is to
> remove stuff *after* the build, which is of course way to late. The files
> should be removed in the build target instead.
>
I've updated debian/rules to remove celt/config.log and celt/config.status
before build celt, and celt/config.{log, status} will be deleted in
debian/rules
clean and build target.
The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/s/spice
- Source repository: deb-src http://mentors.debian.net/debian unstable
main contrib non-free
- dget http://mentors.debian.net/debian/pool/main/s/spice/spice_0.8.2-1.dsc
And its git repository is:
git://git.debian.org/collab-maint/spice.git
http://git.debian.org/?p=collab-maint/spice.git;a=summary
Thanks,
--
Liang Guo
http://bluestone.cublog.cn
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAJwrgW7=hit5tf2uq0goahzq+y-nemfdiffeuf1mjmphpp1...@mail.gmail.com
Re: RFS: spice
On Sat, Jul 23, 2011 at 4:54 PM, Kilian Krause wrote: > Hi Liang, > > On Sat, Jul 23, 2011 at 04:18:11PM +0800, Liang Guo wrote: >> I am looking for a sponsor for my package "spice". > >> I override configure-generated-file-in-source lintian >> warnings, for spice_0.8.2.orig-celt.tar.gz come with >> config.log and config.status and debian/rules will >> delete them. >> - dget http://mentors.debian.net/debian/pool/main/s/spice/spice_0.8.2-1.dsc > > You shouldn't need to override these warnings if the clean target would just > seriously delete them (not as make distclean but plain rm -f). Alternatively > you could stuff them into debian/clean. That should get rid of the warning > and thus the need to override. The lintian warning configure-generated-file-in-source is caused by upstream celt package, it comes with config.log and config.status, to remove this lintian warning, I need repack spice_0.8.2.orig-celt.tar.gz which I think it is not nessary. > > What makes me wonder more though is that you put autotools-dev into the > Build-Depends yet do not seem to make use of it. Removed, > > Moreover you specify this package is only suitable to build on i386 and > amd64. Most probably these are the only platforms that you've built and > tested this on - but apart from this, is there any known limitation why it > would not be buildable on any other arch? Shouldn't the source be arch:any > rather? Spice embedded some ASM code (very little, only 4 lines at all), so it can only be compiled in x86 and x86_64 now. When multiplatform support added, I'll update Architecture field soon. > > Regarding the embedded celt I'm probably as unhappy with the solution as the > rest and I'm inclined to say it should be packaged separately to scale > better. Yet I also see that'd be stepping quite a lot onto the celt > maintainers (who don't want the celt051 in the first place). > > Your patches are not marked as forwarded upstream. I guess upstream would be > interested in them though. I'll forward these patches upstream soon, Thanks pointout that. > > So please try to find out about the arch:all issue, add the missing > autotools-dev files replacement and report back to get the upload prepared. > I've uploaded new spice to mentors.d.n, the download URL is still valid. I've pushed the changes to git repository too, its git repository is: git://git.debian.org/collab-maint/spice.git http://git.debian.org/?p=collab-maint/spice.git;a=summary Thanks, -- Liang Guo http://bluestone.cublog.cn -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cajwrgw7nfhq-j5o3lb7pg+gnk-ghuffureolqucwimbatsc...@mail.gmail.com
RFS: spice
Dear mentors, I am looking for a sponsor for my package "spice". * Package name: spice Version : 0.8.2-1 Upstream Author : Red Hat, Inc. * URL : http://www.spice-space.org/ * License : LGPL 2.1+ Section : misc It builds these binary packages: libspice-server-dev - Header files and development documentation for spice-server libspice-server1 - Implements the server side of the SPICE protocol spice-client - Implements the client side of the SPICE protocol I override configure-generated-file-in-source lintian warnings, for spice_0.8.2.orig-celt.tar.gz come with config.log and config.status and debian/rules will delete them. The upload would fix these bugs: 560721 My motivation for maintaining this package is: SPICE is an interesting desktop virtulization project, I want Debian can act as a guest or hypervisor with SPICE support. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/s/spice - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/s/spice/spice_0.8.2-1.dsc I would be glad if someone uploaded this package for me. Thanks and Regards, -- Liang Guo http://bluestone.cublog.cn signature.asc Description: Digital signature
Re: RFS: spice-protocol (updated package)
On Sat, Jul 23, 2011 at 4:20 AM, Kilian Krause wrote: > Hi Guo, > > On Tue, Jul 19, 2011 at 10:51:03AM +0800, Liang Guo wrote: >> I am looking for a sponsor for the new version 0.8.1-1 >> of my package "spice-protocol". >> >> - dget >> http://mentors.debian.net/debian/pool/main/s/spice-protocol/spice-protocol_0.8.1-1.dsc > > Thanks for the update and appologies for taking so long to review this > simple change. > > Built, signed, uploaded. > > -- > Best regards, > Kilian Thankyou! -- Liang Guo http://bluestone.cublog.cn -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cajwrgw4gg4_2exqz5ckt7bckhyln5wznnzpab4gee0fgh+o...@mail.gmail.com
RFS: spice-protocol (updated package)
Dear mentors, I am looking for a sponsor for the new version 0.8.1-1 of my package "spice-protocol". It builds these binary packages: libspice-protocol-dev - SPICE protocol headers The package appears to be lintian clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/s/spice-protocol - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/s/spice-protocol/spice-protocol_0.8.1-1.dsc I would be glad if someone uploaded this package for me. Thanks and Regards, -- Liang Guo http://bluestone.cublog.cn signature.asc Description: Digital signature
Re: Fwd: RFS: herculesstudio
On Sun, Apr 10, 2011 at 3:28 PM, Thomas Goirand wrote: >> And I've push my changes to git.d.o, you can check it at: >> >> git://git.debian.org/git/collab-maint/herculesstudio.git >> >> Thanks and Regards, > > That's great if you use Git, I maintain all of my packages this was as > well. But next time you ask for sponsorship, please fill the Vcs-Git and > Vcs-Browser fields of debian/control accordingly. I'll add VCS-* fields in next upload. Hercules Studio is almost the first package I made for Debian, most work were done in July 2010, but every thing related froze from then until recently I made a hercules NMU to enable external GUI support. I'm very very glad that it finally uploaded to Debian. > > As the Vcs-* fields were not blockers, I did upload the package to SID > for you. Please correct this in your Git for the next upload. :) > > Thanks for your interest in Debian, and for your work. I am now > confident that you deserve the DM status, and I can for sure vouch for > you, in a more definitive way that I did on my first message. > > Thomas > Thanks you for your help! -- Liang Guo http://bluestone.cublog.cn -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktimszhqdu1weybzkagviiopysiu...@mail.gmail.com
Re: Fwd: RFS: herculesstudio
CC to debian-mentors and BUG:585510 On Sat, Apr 9, 2011 at 1:07 PM, Thomas Goirand wrote: > 1/ Can you use the new DEP5 format for your debian/copyright? > Done > 2/ The policy is now 3.9.1. Done, actually current policy is 3.9.2 now, but lintian don't support it yet. so I still use 3.9.1 > > 3/ I think you should remove useless comments in your debian/rules, it > would improve readability. Like: Unnecessary comments are removed. > 4/ I tried the GUI, and it seemed vaguely working, that's enough for me. > But where exactly in the Gnome menu did it install??? > I added herculesstudio.desktop, so Hercules Studio can be found at System or System/Simulator now. > That's all I can say for the moment. > > Thomas > I've uploaded updated herculesstudio, it can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/h/herculesstudio - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/h/herculesstudio/herculesstudio_1.2.0-1.dsc And I've push my changes to git.d.o, you can check it at: git://git.debian.org/git/collab-maint/herculesstudio.git Thanks and Regards, -- Liang Guo http://bluestone.cublog.cn -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTinOnT3f+-R6Oby_ZS3=9au9a0k...@mail.gmail.com
RFS: herculesstudio
Dear mentors, I am looking for a sponsor for my package "herculesstudio". * Package name: herculesstudio Version : 1.2.0-1 Upstream Author : Jacob Dekel * URL : http://www.mvsdasd.org/hercstudio/ * License : GPL Section : otherosfs It builds these binary packages: herculesstudio - Hercules gui interface The package appears to be lintian clean. The upload would fix these bugs: 585510 My motivation for maintaining this package is: HerculesStudio is the first gui frontend in Linux, it is easy to use, I use it to study IBM z series mainframe knowledge, I think it use useful for others too. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/h/herculesstudio - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/h/herculesstudio/herculesstudio_1.2.0-1.dsc I would be glad if someone uploaded this package for me. Kind regards Liang Guo http://bluestone.cublog.cn signature.asc Description: Digital signature
Re: RFS: spice
On Tue, Mar 8, 2011 at 4:57 AM, Thomas Goirand wrote: > On 03/08/2011 11:56 AM, Liang Guo wrote: >> spice-protocol can be found on mentors.debian.net: >> - URL: http://mentors.debian.net/debian/pool/main/s/spice-protocol >> - Source repository: deb-src http://mentors.debian.net/debian unstable >> main contrib non-free >> - dget >> http://mentors.debian.net/debian/pool/main/s/spice-protocol/spice-protocol_0.8.0-1.dsc >> >> it build libspice-protocol-dev >> >> Thanks and Regards, >> > When building in my Squeeze laptop (I always do that before trying in > SID), it > told me: > > configure: error: Package requirements (pixman-1 >= 0.17.7) were not met: > > Requested 'pixman-1 >= 0.17.7' but version of Pixman is 0.16.4 > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables PIXMAN_CFLAGS > and PIXMAN_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > make: *** [build-stamp] Error 1 > dpkg-buildpackage: error: debian/rules build gave error exit status 2 > > So I am guessing that your build dependencies aren't correct. Please add a > versionned dependency to pixman. > > Thomas > > Fixed and uploaded new packages to mentors.d.n, the link has not change. please review. BTW: I've push spice to git.d.o, you can fetch it with: git clone http://git.debian.org/git/collab-maint/spice.git -- Liang Guo http://bluestone.cublog.cn -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTim6diqj=5ormx1xnr8gfd8kfsi2ah6ppa14s...@mail.gmail.com
Re: RFS: spice
On Tue, Mar 8, 2011 at 3:48 AM, Thomas Goirand wrote: > On 03/08/2011 02:41 AM, Liang Guo wrote: >> Hi, Michael, >> >> On Sun, Mar 6, 2011 at 7:34 PM, Michael Tokarev wrote: >> >>> spice requires on spice-protocol >= 0.7.0, it wont built with >>> spice-protocol 0.6.3 or 0.6.4. Ditto for older spice, 0.6.4 >>> needs spice-protocol=0.6.4, and spice 0.6.3 needs 0.6.3 protocol, >>> it does not comiple if the version condition is not met. >>> >> I just think spice need the same version(at lease big version, such as 0.8) >> spice-protocol to build, so I'll add spice-protocol (>= 0.8.0) to spice >> build-depends. >> >> > Where do I find libspice-protocol-dev ? > > Thomas > > spice-protocol can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/s/spice-protocol - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/s/spice-protocol/spice-protocol_0.8.0-1.dsc it build libspice-protocol-dev Thanks and Regards, -- Liang Guo http://bluestone.cublog.cn -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTi=vbNvHAxik8c5iWEC9=pehj2xyjznc44pv7...@mail.gmail.com
Re: RFS: spice
Hi, Michael,
On Sun, Mar 6, 2011 at 7:34 PM, Michael Tokarev wrote:
> spice requires on spice-protocol >= 0.7.0, it wont built with
> spice-protocol 0.6.3 or 0.6.4. Ditto for older spice, 0.6.4
> needs spice-protocol=0.6.4, and spice 0.6.3 needs 0.6.3 protocol,
> it does not comiple if the version condition is not met.
I just think spice need the same version(at lease big version, such as 0.8)
spice-protocol to build, so I'll add spice-protocol (>= 0.8.0) to spice
build-depends.
>
> I added this versioned build-dependency locally but didn't push
> it out, you come faster.
>
> Please also ensure that spice can be re-built without cleaning,
> right now on any build error it starts with ./configure (in celt)
> again and later fails due due to EEXIST:
>
> build-stamp:
> cd celt && ./configure --prefix=/usr && cd ..
> $(MAKE) -C celt
> ln -s celt/libcelt celt051
> sed 's#\/usr#$(CURDIR)#' celt/celt051.pc |sed 's#/include##'|sed
> 's#/lib#/celt051/.libs#'>celt051.pc
> PKG_CONFIG_PATH=/usr/share/pkgcnfig:/usr/lib/pkgconfig:$(CURDIR)
> ./configure --prefix=/usr --enable-gui
> $(MAKE)
> touch build-stamp
>
> This better be split into 4 different targets depending one on
> another. Again, I did all this locally and I told you about that,
> but you prefer your to do the work twice, -- I'm fine with that.
I updated build-stamp target, and now it can be build again
without clean.
It's well to split build-stamp and clean to several part, would you
like push you changes to git ?
>
> Besides, this PKG_CONFIG thing with generation of celt051.pc and the
> symlink (where it FTBFS twice in a row) aren't needed: use
> CELT051_CFLAGS and CELT051_LDFLAGS pointing to $(CURDIR)/celt/libcelt,
> and ./configure will figure out the rest without additional ugliness.
It's really a elegance method, no need to hijack PKG_CONFIG now.
> Another thing: does libcelt051 development files it installs really
> needed? It looks like they're not used even for spice-dev package,
> but I'm not sure, I haven't looked.
Spice may not use celt051 development files any more, but
other packages may need it. IMO, even though celt051 is
embedded in spice, everything celt051 install as a standalone
package should be installed.
>
> An important note: the source contains 3 autogenerated files
> (server/generated_{,de}marshallers.{c,h}), with proper rules
> to re-generate from spice.proto when out of date. In order
> to re-generate these files, one need python-pyparsing package
> (pyparsing python module), and ofcours python interpreter
> itself. I think this should be added to build-depends, with
> appropriate comment.
In normal situation, these files should be generated by upstream
release manager before every new release, if some day we
changed spice.proto for Debian, we can regenerate
server/generated_{,de}marshallers.{c,h} and create a patch, or
add python-pyparsing to build-depends just as you said. If we
add now, package builder need install unnecessary packages
to build spice, it's boring, especially in clean room build situation.
>
> And one more thing: is it really necessary to list all copyright texts
> from almost every individual source file in debian/copyright? I don't
> know, but the resulting debian/copyright looks quite a bit messy...
>
Some files in spice is released under different license or copyright
by different object, I classify each file by license and copyright
onwer to shorten it, but, as you see, it is still long.
After DEP-5 becomes to Debian standard, debian/copyright may
be simplified.
> I did everything already locally, with just a few tweaks missing,
> and I told you yesterday I'm testing the package. You at least
> may tell the next time you will ignore anyone else's work.
>
It's my mistake, I'm very very sorry for that. such situation will not
happen any more.
I've pushed my changes to git.d.o , hope this change fine.
Before spice can enter Debian, there are still may things to do,
so if you think something don't fit your requirement, fell free to
improve it.
Thanks and Regards,
--
Liang Guo
http://bluestone.cublog.cn
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/AANLkTikm=ZHtMS3OjmK4Nkirb=bpsxckhq7tdjlyf...@mail.gmail.com
Re: RFS: spice
> > SPICE is also berkeley spice... > It looks like berkeley spice is not in offical spice repository. -- Liang Guo http://bluestone.cublog.cn -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTimr_k0R0BC-00FLWZcrbiqgbC616c74Xcf34=+8...@mail.gmail.com
Re: Bug#585510: herculesstudio: changing back from ITP to RFP
Hi, Add CC to p2 and debian-mentors Actually all packaging work had already completed, I had sent RFS to debian-mentors too: http://lists.debian.org/debian-s390/2010/07/msg7.html But before herculesstudio can be used in Debian, hercules should be compiled with external gui support, I had reported a bug 585508 to ask the package owner to enable external gui support, but I got no response. I've pushed herculesstudio source to git repository: git://git.debian.org/git/collab-maint/herculesstudio.git and hercules with some improvement to git repository: git://git.debian.org/git/collab-maint/hercules.git If someone can sponsor this package or continue this work, I'll be very glade. Thanks and Regards, On Sat, Feb 19, 2011 at 5:08 PM, Lucas Nussbaum wrote: > retitle 585510 RFP: herculesstudio -- Hercules gui interface > noowner 585510 > thanks > > Hi, > > This is an automatic email to change the status of herculesstudio back from > ITP > (Intent to Package) to RFP (Request for Package), because this bug hasn't seen > any activity during the last 6 months. > > If you are still interested in adopting herculesstudio, please send a mail to > with: > > retitle 585510 ITP: herculesstudio -- Hercules gui interface > owner 585510 ! > thanks > > However, it is not recommended to keep ITP for a long time without acting on > the package, as it might cause other prospective maintainers to refrain from > packaging that software. It is also a good idea to document your progress on > this ITP from time to time, by mailing <585...@bugs.debian.org>. > > Thank you for your interest in Debian, > -- > Lucas, for the QA team > > > -- Liang Guo http://bluestone.cublog.cn -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikotp79vse6esm_yrorv3jh62tprpwpagvq-...@mail.gmail.com
Re: will different compiler generate different symbols?
2010/7/16 Russ Allbery : > > If so, you won't be alone, and I'm sure we'll end up with a transition > plan. > > I've been holding off on adding symbols for C++ libraries until the > support for C++ symbol patterns is in stable for exactly that reason. It > resolves the problem of different mangling between different C++ versions. > > -- Is it acceptable that a library come without symbols file? I found my package will generate different symbols in different platform(i386 & amd64), if I use symbols generated in amd64, it will not compile in i386; if I use symbols generated in i386, it will not compile in amd64, I have not test other platform, but I think it may have the same problem too. so I want my package have no symbols file. -- Liang Guo http://bluestone.cublog.cn -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimgwd0lcvxz=jm=8mvv7+-uztc6gcxyelsqr...@mail.gmail.com
Re: RFS: herculesstudio -- Hercules gui interface
On 2010年7月21日 星期三 09:33:02 Paul Wise wrote: > Adding features is generally not appropriate for an NMU unless the > maintainer is on LowThresholdNmu: > > http://www.debian.org/doc/developers-reference/pkgs.html#nmu > http://wiki.debian.org/LowThresholdNmu > > For inactive or unreachable developers, please follow these procedures: > > http://www.debian.org/doc/developers-reference/beyond-pkging.html#mia-qa Thanks, Paul, I've mailed Peter De Schrijver , the maintainer of hercules, asked he/she to enable external gui option. Thanks and Regards, -- Liang Guo http://bluestone.cublog.cn signature.asc Description: This is a digitally signed message part.
Re: RFS: herculesstudio -- Hercules gui interface
2010/7/20 Bastian Blank : Hi, Bastian, Thank you for your kindly review! > > Please explain this section. > >> I overrided debian-rules-ignores-make-clean-error lintian warning, for before >> build, Makefile does not exist. > > The error is real, please fix it. I removed this lintian warning, it's fine now. > > Some other things: > - Overriding the MAKE variable is not correct. removed overriding MAKE > - Use dh_install I don't clearly understand your meaning, how should I use dh_install ? > - It considers itself non-working with the current hercules package, > please provide patches. > I've submit a bug 585508[1] on hercules to ask the maintainer to enable external GUI, but get no response until now. should I do a NMU ? I've reuploaded herculesstudio to mentors, would you like to check it again? it can be downloaded from dget http://mentors.debian.net/debian/pool/main/h/herculesstudio/herculesstudio_1.2.0-1.dsc [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585508 Thanks and Regards, -- Liang Guo http://bluestone.cublog.cn -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikngfizkbpdzx9dnzp-wjam3lr5jqrj5yj3m...@mail.gmail.com
RFS: herculesstudio -- Hercules gui interface
Dear mentors, I am looking for a sponsor for my package "herculesstudio". Package name: herculesstudio Version: 1.2.0-1 Upstream Author: Jacob Dekel URL: http://www.mvsdasd.org/hercstudio/ License: GPL Programming Lang : C++ Section : otherosfs It builds these binary packages: herculesstudio - Hercules gui interface I overrided debian-rules-ignores-make-clean-error lintian warning, for before build, Makefile does not exist. The upload would fix these bugs: 585510 My motivation for maintaining this package is: HerculesStudio is the first gui frontend in Linux, it is easy to use, I use it to study IBM z series mainframe knowledge, I think it use useful for others too. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/h/herculesstudio - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/h/herculesstudio/herculesstudio_1.2.0-1.dsc I would be glad if someone uploaded this package for me. Kind regards -- Liang Guo http://bluestone.cublog.cn signature.asc Description: This is a digitally signed message part.
Re: will different compiler generate different symbols?
2010/7/16 Russ Allbery : > >> If it does, which compiler should I use to compile my packages and to >> generate symbols? > > Whatever the current Debian default compiler as installed by > build-essential is. > Current build-essential depends on g++ (>= 4:4.4.3), so I should use g++ 4.4.3. But If build-essential depends on g++ 4.5 in the future, is it mandatory to compile my package with new g++ and regenerate symbols ? -- Liang Guo http://bluestone.cublog.cn -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktill0ldr0gt0y2hoxu5pmrdv21pd0nn9mcnw4...@mail.gmail.com
will different compiler generate different symbols?
it20100627 _znst6vectorin12ipysegmentor8tsegmentesais1_ee15_m_range_insertin9__gnu_cxx17__normal_iteratorips1_s3_vs8_t_s9_st20forward_iterator_...@base 2.0.2~git20100627 _znst6vectorin12ipysegmentor8tsegmentesais1_ee5eraseen9__gnu_cxx17__normal_iteratorips1_s3_ee...@base 2.0.2~git20100627 + _znst6vectorin12ipysegmentor8tsegmentesais1_ee7reserv...@base 2.0.2~git20100627-1 _znst6vectorin12ipysegmentor8tsegmentesais1_ee9push_backerk...@base 2.0.2~git20100627 _znst6vectorin12ipysegmentor8tsegmentesais1_eed...@base 2.0.2~git20100627 _znst6vectoripkcsais1_ee13_m_insert_auxen9__gnu_cxx17__normal_iteratorips1_s3_eerk...@base 2.0.2~git20100627 @@ -346,12 +375,16 @@ _znst6vectorisbijst11char_traitsijesaijeesais3_ee7reserv...@base 2.0.2~git20100627 _znst6vectorisbijst11char_traitsijesaijeesais3_eed...@base 2.0.2~git20100627 _znst6vectorisssaissee13_m_insert_auxen9__gnu_cxx17__normal_iteratoripsss1_eer...@base 2.0.2~git20100627 + _znst6vectorisssaissee7reserv...@base 2.0.2~git20100627-1 + _znst6vectorisssaissee9push_backer...@base 2.0.2~git20100627-1 + _znst6vectorisssaisseed...@base 2.0.2~git20100627-1 _znst6vectorisssaisseeaserk...@base 2.0.2~git20100627 _znst6vectorist4pairiesais1_ee13_m_insert_auxen9__gnu_cxx17__normal_iteratorips1_s3_eerk...@base 2.0.2~git20100627 _znst6vectorist4pairiesais1_eed...@base 2.0.2~git20100627 _znst6vectorist4pairiesais1_eeaserk...@base 2.0.2~git20100627 _znst6vectoriisaiiee13_m_insert_auxen9__gnu_cxx17__normal_iteratoripis1_ee...@base 2.0.2~git20100627 _znst6vectoriisaiiee7reserv...@base 2.0.2~git20100627 + _znst6vectoriisaiieed...@base 2.0.2~git20100627-1 _znst6vectoriisaiieeaserk...@base 2.0.2~git20100627 _znst6vectorijsaijee13_m_insert_auxen9__gnu_cxx17__normal_iteratoripjs1_ee...@base 2.0.2~git20100627 _znst6vectorijsaijee14_m_fill_inserten9__gnu_cxx17__normal_iteratoripjs1_eem...@base 2.0.2~git20100627 @@ -394,15 +427,16 @@ _znst8_rb_treeijst4pairikjiest10_select1stis2_est4lessijesais2_ee8_m_eraseepst13_rb_tree_nodeis...@base 2.0.2~git20100627 _znst8_rb_treeijjst9_identityijest4lessijesaijee10_m_insert_epkst18_rb_tree_node_bases8_...@base 2.0.2~git20100627 _znst8_rb_treeijjst9_identityijest4lessijesaijee8_m_eraseepst13_rb_tree_node...@base 2.0.2~git20100627 - _zst11mem_fun_refiv13tlatticestatessest20const_mem_fun1_ref_tit_t0_t1_ems3_kfs2_s...@base 2.0.2~git20100627 - _zst11mem_fun_refiv13tlexiconstatessest20const_mem_fun1_ref_tit_t0_t1_ems3_kfs2_s...@base 2.0.2~git20100627 +#MISSING: 2.0.2~git20100627-1# _zst11mem_fun_refiv13tlatticestatessest20const_mem_fun1_ref_tit_t0_t1_ems3_kfs2_s...@base 2.0.2~git20100627 +#MISSING: 2.0.2~git20100627-1# _zst11mem_fun_refiv13tlexiconstatessest20const_mem_fun1_ref_tit_t0_t1_ems3_kfs2_s...@base 2.0.2~git20100627 _zst13__adjust_heapin9__gnu_cxx17__normal_iteratorip13tcandipairptrst6vectoris2_sais2_ls2_evt_t0_s9_...@base 2.0.2~git20100627 _zst22__uninitialized_copy_ain9__gnu_cxx17__normal_iteratoripk13tlexiconstatest6vectoris2_sais2_ps2_s2_et0_t_sb_sa_rsait...@base 2.0.2~git20100627 _zst22__uninitialized_copy_aip13tlexiconstates1_s0_et0_t_s3_s2_rsait...@base 2.0.2~git20100627 _zst22__uninitialized_copy_aipn12ipysegmentor8tsegmentes2_s1_et0_t_s4_s3_rsait...@base 2.0.2~git20100627 _zst22__uninitialized_move_aip13clatticeframes1_sais0_eet0_t_s4_s3_r...@base 2.0.2~git20100627 _zst24__uninitialized_fill_n_aip13clatticeframems0_s0_evt_t0_rkt1_rsait...@base 2.0.2~git20100627 - _zst5mergein9__gnu_cxx17__normal_iteratoripn12ipysegmentor8tsegmentest6vectoris3_sais3_s8_st20back_insert_iteratoris7_eet1_t_sc_t0_sd_...@base 2.0.2~git20100627 + _zst4copyin9__gnu_cxx17__normal_iteratoripn12ipysegmentor8tsegmentest6vectoris3_sais3_s8_et0_t_sa_...@base 2.0.2~git20100627-1 +#MISSING: 2.0.2~git20100627-1# _zst5mergein9__gnu_cxx17__normal_iteratoripn12ipysegmentor8tsegmentest6vectoris3_sais3_s8_st20back_insert_iteratoris7_eet1_t_sc_t0_sd_...@base 2.0.2~git20100627 _zst8_destroyist4pairieev...@base 2.0.2~git20100627 _zst8for_eachin9__gnu_cxx17__normal_iteratorip13tlatticestatest6vectoris2_sais2_st9binder2ndist20const_mem_fun1_ref_tivs2_sseeet0_t_sd_...@base 2.0.2~git20100627 _zst8for_eachin9__gnu_cxx17__normal_iteratorip13tlexiconstatest6vectoris2_sais2_st9binder2ndist20const_mem_fun1_ref_tivs2_sseeet0_t_sd_...@base 2.0.2~git20100627 dh_makeshlibs: dpkg-gensymbols -plibsunpinyin3 -Idebian/libsunpinyin3.symbols -Pdebian/libsunpinyin3 returned exit code 1 make: *** [binary-arch] 错误 1 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 Does it mean when using different compiler, the SAME library source code will generate different symbols? If it does, which compiler should I use to compile my packages and to generate symbols? How should I handle this problem ? Regards, -- Liang Guo http://bluestone.cublog.cn -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trou
Re: How to test a manpage? ‘nroff -man | less’ d oes not display like ‘man’.
2010/7/14 Charles Plessy : > Dear all, > > before updating a package, I wanted to look at the new upstream manpage, but > realised that 'nroff -man' does not produce the same output as 'man' itself. > Let's take the example of samtools(1) from the samtools package. > > With 'man samtools', users can see tables like the following one in the > section > 'SAM FORMAT'. > > > ┌┬───┬──┐ > │Col │ Field │ Description >│ > > ├┼───┼──┤ > │ 1 │ QNAME │ Query (pair) NAME >│ > │ 2 │ FLAG │ bitwise FLAG >│ > │ 3 │ RNAME │ Reference sequence NAME >│ > (...) > > But with 'zcat /usr/share/man/man1/samtools.1.gz | nroff -man | less', here > is what > I get. > > center box; cb | cb | cb n | l | l . Col Field Description _ > 1QNAME Query (pair) NAME 2FLAG bitwise FLAG > 3RNAME Reference sequence NAME 4POS 1-based leftmost POSi�\ > > > The workaround I found was to copy the new manpage in /tmp/man/man1, and call > 'man -M /tmp/man samtools'. Does anybody know how a more convenient to > display a > manpage the same way as users will get it by using 'man' ? > > Have a nice day, > > -- > Charles > > > -- > To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/20100714045057.ga25...@merveille.plessy.net > > man -l -- Liang Guo http://bluestone.cublog.cn -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimg4c-ox3cgamxwlurc6m82ky_llzh2q76g5...@mail.gmail.com
Re: RFS: sunpinyin - Simplified Chinese Input Method from SUN
2010/7/12 Thomas Goirand : > Thomas Goirand wrote: >> Liang Guo wrote: >> >>>>> I've re-uploaded my package to mentors.d.n, >>>>> - dget >>>>> http://mentors.debian.net/debian/pool/main/s/sunpinyin/sunpinyin_2.0.2~git20100627-1.dsc >>>>> >>>>> For this package will be uploaded to experimental distribution, would you >>>>> like >>>>> check it in a unstable environment ? >>>>> >>>>> >>>> Under what environment did you test it? Does your package include the >>>> DBUS module? And SCIM? >>>> >>>> >>> I test it in my debian unstable box with ibus front end, This package >>> includes only sunpinyin runtime library. >>> scim frontend is not working with current version sunpinyin >>> >>> I'm working on ibus-sunpinyin, xsunpinyin and open-gram-data(maybe >>> renamed to sunpinyin-data). But they are not good enough. >>> >>> >> Hi, >> >> Your package compiles under SID, but not under Lenny, it's breaking >> when the shlibs depends is being calculated. Can you have a look and >> see what's happening? >> >> I'm currently installing X on a qemu VM to test your package in SID. > Hi, > > The build also failed under SID when dh_makeshlibs was called. Please fix. > > Thomas > > Can you send me the error message ? Thanks, -- Liang Guo http://bluestone.cublog.cn -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktim2yqzljo72xc0sbioehlxo2w83-hwjlpe4a...@mail.gmail.com
Re: RFS: sunpinyin - Simplified Chinese Input Method from SUN
2010/7/10 Thomas Goirand : > Liang Guo wrote: >> LI Daobing said he would like sponsor next time, would you like continue to >> sponsor this time? > > Yes! > >> I've re-uploaded my package to mentors.d.n, >> - dget >> http://mentors.debian.net/debian/pool/main/s/sunpinyin/sunpinyin_2.0.2~git20100627-1.dsc >> >> For this package will be uploaded to experimental distribution, would you >> like >> check it in a unstable environment ? > > Under what environment did you test it? Does your package include the > DBUS module? And SCIM? I test it in my debian unstable box with ibus front end, This package includes only sunpinyin runtime library. scim frontend is not working with current version sunpinyin I'm working on ibus-sunpinyin, xsunpinyin and open-gram-data(maybe renamed to sunpinyin-data). But they are not good enough. > > I'll test it soon myself (only if you tell me it has at least dbus or > scim module included and working though, as otherwise I wont know how to > test...). Would you like try ibus ? maybe you'll like it. > > Thomas -- Liang Guo http://bluestone.cublog.cn -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikn6xtjgxbfi8yjzucq6abfnqhfdzg4hwkzh...@mail.gmail.com
Re: RFS: sunpinyin - Simplified Chinese Input Method from SUN
Hi, Thomas, On 星期一 05 7月 2010 00:52:47 Thomas Goirand wrote: > Liang Guo wrote: > > Hi, Thomas, > > > > Sorry for not reply until now, and Thank you for your kindly review. > > > > http://mentors.debian.net/debian/pool/main/s/sunpinyin/sunpinyin_2.0.2~gi > > t20100627-1.dsc > > Your debian/copyright is still lacking of a copyright notice for the > LGPL-2.1. Added, > > I saw you request, but then that answers ONE of the TWO questions above. > Can you please answer to the 2nd one as well: if they wish to become > maintainer after the first upload, why don't they do the package review > and sponsoring too? I didn't see you asking if they would like to review > your > package... > LI Daobing said he would like sponsor next time, would you like continue to sponsor this time? > >> Replacing the dependency by 0.46.7~ by 0.46-8~bpo50+1 made it work, and > >> should be ok. > > > > I change debian/control to depends on quilt (>= 0.48-7~), 0.48-7 is the > > current git version I use. > > I still couldn't compile it on Lenny. Please set the dependency to: > > quilt (>= 0.46-8~) > > which is enough for the patch feature of Quilt. > > > I resolved almost all lintian warning except > > package-contains-empty-directory, usr/lib/sunpinyin/data is usually used > > to store compiled data from open-gram, but users can use data from other > > sources too, so I think this directory should belongs to libsunpinyin3. > I've re-uploaded my package to mentors.d.n, - dget http://mentors.debian.net/debian/pool/main/s/sunpinyin/sunpinyin_2.0.2~git20100627-1.dsc For this package will be uploaded to experimental distribution, would you like check it in a unstable environment ? Regards, -- Liang Guo http://bluestone.cublog.cn signature.asc Description: This is a digitally signed message part.
Can a package be uploaded to unstable before it works correctly in stable ?
Dear Mentors, I'm packaging sunpinyin, a Chinese input method, and Thomas Goirand is sponsoring it. sunpinyin can be compiled and packaged in my Debian unstable environment, but it fails when build in lenny environment[1] I build a clean lenny environment, and try to compile and package sunpinyin, but dpkg-buildpackage failed in build dependency check, sunpinyin need debhelper (>= 7.0.50~) and quilt (>= 0.0.46-7). debehelper(>=7.0.50~) is added by dh_make, and quilt (>= 0.0.46-7) is added to eliminate a lintian warning. But the versions in lenny is debhelper 7.0.15 and quilt 0.46-6, so sunpinyin failed in build dependency check stage. The versions in lenny-backports is debhelper 7.4.11~bpo50+1 and quilt 0.46-8~bpo50+1, they fit the build dependency. But is backports.org a part of debian NOW? should it be used in a clean room environment ? It looks a little hard to make sunpinyin be compiled and packaged in lenny, so before I do, I want to know can a package be uploaded to unstable before it works correctly in stable? If No, I'll fix this problem as soon as possible. [1]http://lists.debian.org/debian-mentors/2010/07/msg00042.html Regards, -- Liang Guo http://bluestone.cublog.cn signature.asc Description: This is a digitally signed message part.
Re: RFS: sunpinyin - Simplified Chinese Input Method from SUN
t http://googlecode.debian.net/p/open-gram/dict.utf8.tar.bz2 > >> wget http://googlecode.debian.net/p/open-gram/lm_sc.t3g.arpa.tar.bz2 > >> > >> into specific Debian packages on which you would depend? > >> > >> What are the licenses of lm_sc.t3g.arpa.tar.bz2 and dict.utf8.tar.bz2? > >> Would the library continue to work without these files? > > > > lm_sc.t3g.arpa.tar.bz2 and dict.utf8.tar.bz2 is licensed under Creative > > Commons 3.0 BY-SA, CC-by-SA 3.0 is DFSG-compatible[6], I want to package > > it latter, so I write debian/README.Debian as a transient proposal. > > Please do package them and depend on them yes. I'll package open-gram-data, ibus-sunpinyin and xsunpinyin ASAP, After scim- sunpinyin offical released, I'll package it too. Regards, -- Liang Guo http://bluestone.cublog.cn -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201007041550.34721.bluestonech...@gmail.com
RFS: herculesstudio -- Hercules gui interface
Dear mentors, I am looking for a sponsor for my package "herculesstudio". Package name: herculesstudio Version: 1.1.0-1 Upstream Author: Jacob Dekel URL: http://www.mvsdasd.org/hercstudio/ License: GPL Programming Lang : C++ Section : otherosfs It builds these binary packages: herculesstudio - Hercules gui interface I overrided debian-rules-ignores-make-clean-error lintian warning, for before build, Makefile does not exist. The upload would fix these bugs: 585510 My motivation for maintaining this package is: HerculesStudio is the first gui frontend in Linux, it is easy to use, I use it to study IBM z series mainframe knowledge, I think it use useful for others too. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/h/herculesstudio - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/h/herculesstudio/herculesstudio_1.1.0-1.dsc I would be glad if someone uploaded this package for me. Kind regards -- Liang Guo http://bluestone.cublog.cn signature.asc Description: This is a digitally signed message part.
Re: RFS: sunpinyin - Simplified Chinese Input Method from SUN
On 星期三 30 6月 2010 21:57:27 Thomas Goirand wrote: > Hi Liang Guo, Hi, Thomas, (add CC to debian-mentors and pkg-ime-devel) Thanks for your review. > > Here's what I can say when I review your package. > > * debian/copyright: > > Please add a copyright notice for the LGPL-2.1. Which part of LGPL-2.1 should I add ? the end part of LGPL.LICENSE is the same as that of OPENSOLARIS.LICENSE. > > * debian/control: > > You did a confusion between Maintainer: and Uploaders: field. If you write: > > Maintainer: Liang Guo > > you assume the maintainer-ship responsability for the package in Debian. > If you are doing an RFS, then it should be you in this field. Besides > this, you are more than welcome to use UTF-8 and write your name in > Simplified Chinese this file, I believe. > > Uploaders:, if I sponsor the package, would be me, and you don't want to > fill this field. As I didn't sponsor a package yet, I'll have to find > out how to manage this field! :) Maintainer is the owner of this package. for sunpinyin is a input method package, I hope this packageCollaborative maintenanced by IME Packaging Team, so I set IME Packaging Teamas as the Maintainer, and me as the Uploaders. I reference developers-reference[1] to set these fields. For sponsor a package, this FAQ[2] may help. Develpers-reference have related topics[3] too. > > You wrote build-depends on debhelper (>= 7.0.50~) and quilt (>= > 0.46-7~), do you need specificities on specific versions currently in > Debian? If yes, which one? I use dh_make to generate debian/*, ande debian/control comes with build- depends on debhelper, if build-depends on debhelper removed, lintian reports package-uses-debhelper-but-lacks-build-depends, and it will fail to build in my pbuilder environment. My debian/rules invokes dh_quilt_patch and dh_quilt_unpatch when build and clean, those commands are in quilt, so I should have build-depends on quilt [4] > > I never seen/packaged a software using the CDDL type of license. Do you > know if this is a know license that is ok in Debian? CDDL is a commonly used open source license, openoffice, glassfish, netbeans and many other packages in debian use CDDL too. Thomas Koch even raise a bug to ask base-files include CDDL[5] > > * debian/docs: > > You are including LGPL.LICENSE in the list of files install, even though > in your debian/copyright, you mention the path to the LGPL-2.1. In other > words: > - Remove LGPL.LICENSE from debian/docs > - Add the copyright notice for the LGPL (that's a kind of short version > of the big file in /usr/share/common-licenses/LGPL-2.1) in your > debian/copyright. > - I don't think packaging COPYING in your binaries is useful. Remove it > also from debian/docs. OK, I'll remove LGPL.LICENSE and COPYING from debian/docs. Shoud OPENSOLARIS.LICENSE be removed too ? for debian/copyright have included it. > > * README.Debian > > Do you think you could package the files here: > > wget http://googlecode.debian.net/p/open-gram/dict.utf8.tar.bz2 > wget http://googlecode.debian.net/p/open-gram/lm_sc.t3g.arpa.tar.bz2 > > into specific Debian packages on which you would depend? > > What are the licenses of lm_sc.t3g.arpa.tar.bz2 and dict.utf8.tar.bz2? > Would the library continue to work without these files? lm_sc.t3g.arpa.tar.bz2 and dict.utf8.tar.bz2 is licensed under Creative Commons 3.0 BY-SA, CC-by-SA 3.0 is DFSG-compatible[6], I want to package it latter, so I write debian/README.Debian as a transient proposal. > > * debian/rules > - Instead of invoking `pwd` on each files, use $(CURDIR). Its my mistake, I'll correct this problem in next upload. > > * I don't think you need to name the directories in the *.dirs if you > are installing things in it. The directory will be created automatically. There is no file in /usr/lib/sunpinyin/data after installation, it is used for compiled LM and DICD data, and I hope it can be automatically remove if it is empty when remove libsunpinyin3 or sunpinyin-utils. > > (ogiz) dnarioG samohT > > P.S: I'm up-side down because I just drove the full day from 郑州 to 上海... [1] http://www.debian.org/doc/developers-reference/pkgs.html#collaborative- maint [2] http://people.debian.org/~mpalmer/debian-mentors_FAQ.html [3] http://www.debian.org/doc/developers-reference/beyond- pkging.html#sponsoring [4]http://wiki.debian.org/Projects/DebSrc3.0#Doesa3.0.28quilt.29sourcepackageneedtobuild- dependonquilt.3F [5]http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=578522 [6] http://wiki.debian.org/DFSGLicenses -- Liang Guo http://bluestone.cublog.cn signature.asc Description: This is a digitally signed message part.
Re: RFS: sunpinyin - Simplified Chinese Input Method from SUN
On 星期二 29 6月 2010 13:45:15 Thomas Goirand wrote:
> Even though SCIM might soon reach end of life soon as upstream doesn't seem
> very active according to what I could read from others (can't remember
> where: on IRC or in a Debian list, but for sure in Debian) it is still use
> a lot. So I believe it might be a very good idea to also package the SCIM
> module, also because it could well be ported to other platforms (I'm
> namely thinking about Maemo (I'm using my Nokia N900 to write this
> email...)). Also, I think its a shame to package only a part of a program
> only because you use a part of it. Do you think you could as well port the
> SCIM module? I will test it for you (in both Lenny and lucid lynx), and
> help.
In fact, I want to build all frontend of sunpinyin, ibus, scim, xim, and
standalone. As I mentioned, ibus-sunpinyin is just used to verify whether
sunpinyin works or not. If you prefer to upload sunpinyin and its frontend
together, I'll package and upload scim, xim and standalone frontend ASAP.
>
> > ibus-sunpinyin may need minor tuning on Build-Depends and Depends
> > fields in debian/control before they can be considered in good shape.
> > ibus-sunpinyin depends on libsunpinyin-dev, so I don't have a simple
> > methord to compile it in pbuilder.
>
> Just don't use pbuilder and use a (much simpler) chroot then. debootstrap
> is your friend here. I am not a fan of pbuilder, I use a freshly setup VM
> to do the same kind of test pbuilder would, when I need to check for
> dependencies. Remember to desactivate automatic install of recommends if
> you do like me. Put this:
>
> APT
>{
> Install-Recommends "false";
>}
>
> in /etc/apt/apt.conf.d/20norecommends (for example) to do so, then install
> ONLY what is already in the build-deps of your package to check...
Thanks, I'll have a try.
>
> > And I don't know how the upstream maintainer will release sunpinyin in
> > next release, sunpinyin and all its frontend in one package or in
> > different package. If they release everything in one package, I may
> > consider put everything in one source package. This is the reason I
> > prefer to upload to experimental too.
>
> Well, in that case do get in touch with upstream. I do consider that
> upstream responsiveness is so important! Pinging them/him once is the
> minimum you should do, and you MUST be able to receive a valid, timely,
> answer. If you don't get any answer or consideration from them/him, just
> forget about doing the package maintenance work, unless you feel you are
> capable of forking and maintaining the full project!
I'll ask upstream author about this problem, in fact, Kov Chai is one of the
upstream author.
--
Liang Guo
http://bluestone.cublog.cn
signature.asc
Description: This is a digitally signed message part.
Re: RFS: sunpinyin - Simplified Chinese Input Method from SUN
On 星期二 29 6月 2010 03:54:33 Thomas Goirand wrote: > Liang Guo wrote: > > It builds these binary packages: > > libsunpinyin-dev - Simplified Chinese Input Method from SUN > > libsunpinyin3 - Simplified Chinese Input Method from SUN > > sunpinyin-utils - Simplified Chinese Input Method from SUN > > > > The initial ITP is not reported by me, I've contacted with the original > > reporter kefu chai and he allowed me to work on this package[1]. > > > > I've uploaded ibus-sunpinyin too, which can be downloaded with > > dget http://mentors.debian.net/debian/pool/main/i/ibus-sunpinyin/ibus- > > sunpinyin_2.0.2~git20100628-1.dsc > > Even it is not in good shape(lack of some Build-Depends and Depends and > > cannot > > > be compiled in my pbuilder), it can be used to verify sunpinyin. > > > > I would be glad if someone uploaded this package for me. > > Kind regards > > Hi, Hi, Thomas, > > how does this compares to, let's say, scim-pinyin, or the other pinyin > modules > that we can find currently in the archive? sunpinyin is a statistical language model(SLM) based input method, it show you the candidate based on its usage frequency in common life, which makes it smarter then other pinyin input method. For detailed information on SLM, please visit http://code.google.com/p/sunpinyin/wiki/CodeTourOfSLMTraining > > Is it better or at least as good as googlepinyin in Window? (I'm not > talking > about the one in Unix that I already packaged but that is buggy, and > which I > might give-up on). I have not used googlepinyin, I use sougou in Windows, it is hard to compare sougou and sunpinyin, both of them are fast. > > What other alternative do we have in the archive for typing in Chinese > using > ibus? (I only used SCIM so far) there is a pinyin imput method, it works and it is fast, but not smart(IMO), for example, I usually need press "Pg Dn" several times to find the word I want input. Sunpinyin have a SCIM front end too, for I don't use SCIM, I cannot test it simply. > > I might be interested in doing this sponsoring, as my wife is Chinese > and uses > Ubuntu, and that I often (have to) type in Chinese as well. > > Just one thing: I don't think it is a good idea to sponsor onlythe > library without > the ibus module. I strongly believe that these should be packaged and > sponsored > at the same time. In other words: I wont sponsor or even look at your > package > until you say that ibus-sunpinyin is ready as well. ibus-sunpinyin may need minor tuning on Build-Depends and Depends fields in debian/control before they can be considered in good shape. ibus-sunpinyin depends on libsunpinyin-dev, so I don't have a simple methord to compile it in pbuilder. And I don't know how the upstream maintainer will release sunpinyin in next release, sunpinyin and all its frontend in one package or in different package. If they release everything in one package, I may consider put everything in one source package. This is the reason I prefer to upload to experimental too. > > Note: I'm a new DD since last Sunday, so I'll have to learn on how to > make my > first sponsoring as well! :) > > Last thing: where do you live? I'm in Shanghai, even though I'm a > French guy. > I'd like to push more Chinese to use, promote, and enhance Debian... I've shortly stayed in Shanghai in the begin of this year. It is a beautiful city. I'm in ShenZhen now. > > Thomas Goirand (zigo) Thankyou for your review on my package. -- Liang Guo http://bluestone.cublog.cn signature.asc Description: This is a digitally signed message part.
RFS: sunpinyin - Simplified Chinese Input Method from SUN
Dear mentors, I am looking for a sponsor for my package "sunpinyin". * Package name: sunpinyin Version : 2.0.2~git20100627-1 Upstream Author : Lei Zhang Ervin Yan Yong Sun Kefu Chai Wei Xue Leo Zheng chumsdock Mike Qin * URL : http://code.google.com/p/sunpinyin * License : LGPL-2.1 or CDDL Section : libs It builds these binary packages: libsunpinyin-dev - Simplified Chinese Input Method from SUN libsunpinyin3 - Simplified Chinese Input Method from SUN sunpinyin-utils - Simplified Chinese Input Method from SUN The package appears to be lintian clean. The upload would fix these bugs: 478811 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/s/sunpinyin - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/s/sunpinyin/sunpinyin_2.0.2~git20100627-1.dsc The initial ITP is not reported by me, I've contacted with the original reporter kefu chai and he allowed me to work on this package[1]. I've uploaded ibus-sunpinyin too, which can be downloaded with dget http://mentors.debian.net/debian/pool/main/i/ibus-sunpinyin/ibus- sunpinyin_2.0.2~git20100628-1.dsc Even it is not in good shape(lack of some Build-Depends and Depends and cannot be compiled in my pbuilder), it can be used to verify sunpinyin. I would be glad if someone uploaded this package for me. [1] http://lists.debian.org/debian-mentors/2010/06/msg00460.html Kind regards -- Liang Guo http://bluestone.cublog.cn signature.asc Description: This is a digitally signed message part.
Re: RFS: sunpinyin -- An input method engine for Simplified Chinese
2010/3/27 Kov Chai : > Dear mentors, > > I am looking for a sponsor for my package "sunpinyin". > Hi, Kov, Are you still working on sunpinyin ? Thanks, -- Liang Guo http://bluestone.cublog.cn -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimvz7xn6plfdpzovpa3r47ncosmrjc4yeabd...@mail.gmail.com
Re: About package with potential legal risk
On 星期三 09 6月 2010 08:27:41 Craig Small wrote: > On Wed, Jun 09, 2010 at 10:04:36AM +1000, Ben Finney wrote: > > Rather, I think Noel is saying that replacing them quickly, with any > > freely-licensed functional images (even ugly ones), is best. Once > > freely-licensed replacement images are working, other people can suggest > > improvements and do the work of making better images if needed. > > There used to be a website where Free Software projects could ask for > icons. The tree icon for pstree in the psmisc package came from there, > for example. Unfortunately it appears to have gone. > > It's a shame really, as I'm sure there would be some graphically > talented people out there that wouldn't mind drawing icons etc for a > project every now and then, but there doesn't seem a way to find them. > > procps (See bug #192635) has wanted a menu icon since 2003. > > - Craig Thanks to everyone, I'll find some free(in law) icons and pictures for openfetion. Thanks, -- Liang Guo http://bluestone.cublog.cn signature.asc Description: This is a digitally signed message part.
About package with potential legal risk
Dear All, I'm packaging a software openfetion[1], a instant messaging client with ChinaMobile fetion protocol support. Openfetion includes some images or pictures which are copied from ChinaMobile Fetion client, but this has not noticed in any form in openfetion. Should I remove these files or not ? If these files are removed, openfetion works with all function, but have a ugly user interface. ChinaMobile Fetion client[2] is proprietary software on Microsoft windows, it is free of charge to download and use. Thanks, [1] http://basiccoder.com/openfetion [2] http://www.fetion.com.cn/ -- Liang Guo http://bluestone.cublog.cn signature.asc Description: This is a digitally signed message part.
Re: RFS: xserver-xorg-video-qxl
On Monday 24 May 2010 21:08:50 Julien Cristau wrote: > > Uploaded, thanks. Thanks, > > Not quite sure how to deal with the 3.0 (quilt) sillyness of deleting > the autogen.sh script and moving it to > debian/patches/debian-changes-0.0.12-1 during the build (the script is > in upstream git, but not in tarballs, so shows up as a diff), but I > don't care enough. -- Liang Guo http://bluestone.cublog.cn signature.asc Description: This is a digitally signed message part.
Re: RFS: xserver-xorg-video-qxl
On Friday 21 May 2010 04:08:53 Julien Cristau wrote: > > You're calling dh_prep in debian/rules clean, this is wrong, should be > replaced by dh_clean. dh_prep is used in the install target before > running make install, and obsoletes 'dh_clean -k', not all invocations > of dh_clean. Corrected, Thank you. Could you please check it again ? > > Let me know when that's fixed I'll upload the package to the archive (I > assume you've tested the driver in a RHEV environment, and it worked for > you?). I have test it within vdesktop 0.4(http://www.spice-space.org/download.html), at lease it works. Thanks, -- Liang Guo http://bluestone.cublog.cn signature.asc Description: This is a digitally signed message part.
Re: RFS: xserver-xorg-video-qxl
On Tuesday 18 May 2010 20:05:43 Julien Cristau wrote:
> Hi,
>
> I just had a quick look at the git repo. The packaging looks sane
> enough. The git tree is kind of a mess though. It would be nicer IMO
> to directly pull from the upstream git tags at
> git://anongit.freedesktop.org/git/xorg/driver/xf86-video-qxl, rather
> than dump the contents directly. Same goes for debian/xsfbs/ stuff.
>
> Also the code is moved to a versioned xserver-xorg-video-qxl-0.0.12
> subdir inside your git tree, which is not the way to go IMO.
>
> debian/patches/series mentions fix_qxl_driver_assert.patch, but that
> patch is not in the repo (I assume it's upstream's "qxl: remove asserts
> that make no sense anymore" commit).
>
Hi, Julien,
Thanks for your review. For this package is a xorg driver, I've created a new
git repository at git://git.debian.org/git/pkg-xorg/driver/xserver-xorg-video-
qxl.git, this repository has three branch, upstream-unstable hold local copy
of the upstream qxl, xsfbs-unstable hold local copy of debian xsfbs, and
debian-unstable hold the debian directory in addition to the full source tree
from upstream.
I've upload this package to mentors too,
- URL: http://mentors.debian.net/debian/pool/main/x/xserver-xorg-video-qxl
- Source repository: deb-src http://mentors.debian.net/debian unstable main
contrib non-free
- dget http://mentors.debian.net/debian/pool/main/x/xserver-xorg-video-
qxl/xserver-xorg-video-qxl_0.0.12-1.dsc
For this package have never enter official debian repositories, I think it is
proper to use version number 0.0.12-1. I have not create tag in git
repository, I think I should create a tag when this package is good enough to
enter into debian.
There is a strange file debian/xserver-xorg-video-qxl.debhelper.log in
generated package xserver-xorg-video-qxl_0.0.12-1.debian.tar.gz, shoud I
remove it?
> Some minor stuff that could be updated for recent changes in other
> pkg-xorg drivers:
> - rename the build dir from 'obj-$(DEB_BUILD_GNU_TYPE)' to 'build' or
> similar, there's no reason to have the build machine type in there
> (that's just a cosmetic change)
done
> - update xsfbs.mk to the latest version, build-depend on
> xserver-xorg-dev 2:1.7.6.901, and use ${xviddriver:Depends} instead of
> ${xserver:Depends}. This should allow us to handle ABI changes
> without Conflicts/Breaks in the future, see #573371.
done
> - drop the http://xorg.freedesktop.org and mailman urls from
> debian/control
done
Thanks for your review.
--
Liang Guo
http://bluestone.cublog.cn
signature.asc
Description: This is a digitally signed message part.
Re: RFS: xserver-xorg-video-qxl
在 星期三 05 5月 2010 09:46:59，Paul Wise 写道：
> On Wed, Apr 21, 2010 at 4:33 PM, Liang Guo wrote:
> > I am looking for a sponsor for my package "xserver-xorg-video-qxl".
>
> I'm not doing any additional sponsoring, but here is a quick review:
Thankyou, Paul!
>
> sed -i -e s/SPICE-compitable/SPICE-compatible/ debian/control
done
>
> Should XSF packages have the team address in Maintainer?
changed
>
> One of the files is public domain, you should document that in
> debian/copyright.
done
>
> Since you are using dpkg-source v3 (quilt), you can drop the first
> paragraph of debian/README.source.
for this package's maintainer is changed to XSF, I copy this file from other
XSF maintained package.
>
> Any idea why upstream installs a .la file for the driver? Surely that
> isn't needed. Do the RedHat/Fedora install it? This generates a
> warning:
>
> dh_install: usr/lib/xorg/modules/drivers/qxl_drv.la exists in
> debian/tmp but is not installed to anywhere
>
> gcc warnings to send upstream (preferrably with patch):
>
> ../../src/lookup3.c:171: warning: no previous prototype for 'hashword'
> ../../src/lookup3.c:215: warning: no previous prototype for 'hashword2'
> ../../src/lookup3.c:462: warning: no previous prototype for 'hashlittle2'
> ../../src/lookup3.c:646: warning: no previous prototype for 'hashbig'
> ../../src/qxl_mem.c: In function 'qxl_mem_dump_stats':
> ../../src/qxl_mem.c:96: warning: pointer of type 'void *' used in
> arithmetic ../../src/qxl_mem.c:96: warning: comparison of distinct pointer
> types lacks a cast
> ../../src/qxl_mem.c: In function 'qxl_alloc':
> ../../src/qxl_mem.c:152: warning: pointer of type 'void *' used in
> arithmetic ../../src/qxl_mem.c: In function 'qxl_free':
> ../../src/qxl_mem.c:242: warning: pointer of type 'void *' used in
> arithmetic ../../src/qxl_mem.c:262: warning: pointer of type 'void *' used
> in arithmetic ../../src/qxl_mem.c:294: warning: pointer of type 'void *'
> used in arithmetic ../../src/qxl_driver.c:484: warning: 'print_region'
> defined but not used ../../src/qxl_driver.c:540: warning: 'paint_shadow'
> defined but not used
>
I'll send these message to upstream and ask them to correct.
> dpkg-gencontrol warning:
>
> dpkg-gencontrol: warning: package xserver-xorg-video-qxl: unused
> substitution variable ${xinpdriver:Provides}
>
> lintian complaints:
>
> I: xserver-xorg-video-qxl: description-possibly-contains-homepage
> http://www.X.org
> P: xserver-xorg-video-qxl: no-homepage-field
> P: xserver-xorg-video-qxl: no-upstream-changelog
There is no upstream changelog, so I cannot include it in my package.
> X: xserver-xorg-video-qxl: shlib-calls-exit
> usr/lib/xorg/modules/drivers/qxl_drv.so
I've upload a new version xserver-xorg-video-qxl to mentor, it can be get from
http://mentors.debian.net/debian/pool/main/x/xserver-xorg-video-qxl/xserver-
xorg-video-qxl_0.0.12-2.dsc
its git repository is
git://git.debian.org/git/collab-maint/xserver-xorg-video-qxl.git
Cyril, would you like to review my package when you have time ?
Thanks,
--
Liang Guo
http://bluestone.cublog.cn
signature.asc
Description: This is a digitally signed message part.
Re: RFS: xserver-xorg-video-qxl
Hi! 2010/4/22 Cyril Brulebois > Hi! > > (Keeping you Cc'd for now, I'm not sure which lists you're subscribed > to.) > > Liang Guo (21/04/2010): > > - dget http://mentors.debian.net/debian/pool/main/x/xserver-xorg-video- > > qxl/xserver-xorg-video-qxl_0.0.12-1.dsc > > I had a *very* quick look, and it didn't sound too bad. I'd have to > double-check it of course, but it'd be nice if there were some git > branches available somewhere, that'd ease reviewing. > > Maybe you could start by publishing your branches on alioth's > collab-maint or as public user git repository there? > > Mraw, > KiBi. > > Have you checked my package ? Any sugestion ? Thanks, -- Liang Guo http://bluestone.cublog.cn
Re: RFS: xserver-xorg-video-qxl
在 星期四 22 四月 2010 08:21:54，Cyril Brulebois 写道： > Hi! > > (Keeping you Cc'd for now, I'm not sure which lists you're subscribed > to.) > > Liang Guo (21/04/2010): > > - dget http://mentors.debian.net/debian/pool/main/x/xserver-xorg-video- > > qxl/xserver-xorg-video-qxl_0.0.12-1.dsc > > I had a *very* quick look, and it didn't sound too bad. I'd have to > double-check it of course, but it'd be nice if there were some git > branches available somewhere, that'd ease reviewing. > > Maybe you could start by publishing your branches on alioth's > collab-maint or as public user git repository there? Thankyou for your review and advice. I've created a git repository on collab-maint, git://git.debian.org/git/collab-maint/xserver-xorg-video-qxl.git I'll add Vcs-* fields in the next update. Thanks, -- Liang Guo http://bluestone.cublog.cn signature.asc Description: This is a digitally signed message part.
RFS: xserver-xorg-video-qxl
Dear mentors, I am looking for a sponsor for my package "xserver-xorg-video-qxl". * Package name: xserver-xorg-video-qxl Version : 0.0.12-1 Upstream Author : [fill in name and email of upstream] * URL : http://cgit.freedesktop.org/xorg/driver/xf86-video-qxl/ * License :MIT Section : x11 It builds these binary packages: xserver-xorg-video-qxl - X.Org X server -- QXL display driver The package appears to be lintian clean. The upload would fix these bugs: 576642 My motivation for maintaining this package is: I hope Debian have a excelient graphical experience in SPICE-enabled KVM simulator. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/x/xserver-xorg-video-qxl - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/x/xserver-xorg-video- qxl/xserver-xorg-video-qxl_0.0.12-1.dsc I would be glad if someone uploaded this package for me. Kind regards -- Liang Guo http://bluestone.cublog.cn signature.asc Description: This is a digitally signed message part.
Re: RFS: tgt (updated package,NMU)
Hi, Tim, There are only little difference between these package: 1 My package use upstream version 0.9.11, and Ben's package use upstream version 0.9.10. 2 Ben's package add some patch to elimate lintian warnings: binary-without- manpage , executable-not-elf-or-script, possible-gpl-code-linked-with-openssl. The depending on openssl may be removed in the next upstream release. 3 My package don't enable FCOE feature. 4 My package contain a init.d script based on the upstream source. I've mailed Kernel Team to ask whether they would like to upgrade tgt to upstream version, but got no response. Hi, Ben, Would you like to sponsor my package, or to upload your package ? After all, tgt in unstable is too old. Thanks, Liang Guo 在 星期三 09 十二月 2009 03:36:33，Tim Retout 写道： > On Wed, Dec 09, 2009 at 01:01:21AM +0800, Liang Guo wrote: > > Dear mentors, > > > > I am looking for a sponsor for the new version 1:0.9.11-0.1 > > of my package "tgt". > > [Adding Ben Hutchings to CC.] > > How does this differ to the upload Ben has prepared in bug #526562? > > I think you should talk to him and the kernel team first - they may > want to sponsor your work if you are interested in helping with tgt > in the future. > > Regards, > signature.asc Description: This is a digitally signed message part.
RFS: tgt (updated package,NMU)
Dear mentors, I am looking for a sponsor for the new version 1:0.9.11-0.1 of my package "tgt". It builds these binary packages: tgt- Linux target framework user-space tools There are some lintian warnings, which may be fixed in the next upstream release. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/t/tgt - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/t/tgt/tgt_0.9.11-0.1.dsc I would be glad if someone uploaded this package for me. Kind regards Liang Guo signature.asc Description: This is a digitally signed message part.
Re: Creating directory with different owner
would it be included in debian/dirs, and then change its owner in postinst ? 2009/12/4 Zaar Hai > Good day dear mentors! > > I'm working on package that needs /var/lib/foo directory, owned by foo > user (which is created during package install). What is the proper way > to package such thing? I've thought about putting it to preinst > script, but then that directory will be not be tracked by dpkg (dpkg > -S will not find it, for example). On the other hand, user foo may not > even exist on build host. > > Thank you, > -- > Zaar > > > -- > To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > > -- Liang Guo http://bluestone.cublog.cn
Re: About software from other distribution
Thanks, I'll working on it. 2009/11/11 Boyd Stephen Smith Jr. > On Tuesday 10 November 2009 10:39:58 Liang Guo wrote: > > Currently I'm using qspice, a Simple Protocol for Independent Computing > > Environments (SPICE) client as my console to connect to KVM. qspice is a > > utility from RedHat Enterprise Linux 5.4, and It is licensed under GNU > > GPLv2. > > > > qspice and related libraries can be downloaded from > > ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/os/SRPMS/ as > > SRPM format, may I package it for Debian ? > > It doesn't matter who upstream is, as long as the software is DFSG-free > [1], > the maintainer is willing to do the work, and it would be useful for Debian > users [2] it can be considered for Debian. Even if it is not DFSG-free, it > might be allowed in non-free. > > [1] In practice, patent or trademark claims could make something not > DFSG-free > even if the copyright holder uses a good license. Or, (ala PINE) the > copyright holder could have an odd view of a normally acceptable license. > > [2] If there's already a package that fills the same role, your package > might > not be considered useful for Debian users. > -- > Boyd Stephen Smith Jr. ,= ,-_-. =. > b...@iguanasuicide.net ((_/)o o(\_)) > ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' > http://iguanasuicide.net/\_/ > > -- Liang Guo http://bluestone.cublog.cn
