Re: schroot: 20copyfiles: cp: cannot create regular file '.../etc/resolv.conf'

2016-09-13 Thread Daniel Shahaf 
Sean Whitton wrote on Tue, Sep 13, 2016 at 17:08:03 -0700:
> Does etc exist in /srv/chroot/unstable-amd64 (or wherever you have the
> base chroot)?

No, it doesn't exist:

% tar tf unstable-amd64.tar.gz | cut -d/ -f 1,2 | uniq -c
  1 ./
   2668 ./usr
 65 ./sbin
  1 ./build
  1 ./mnt
  5 ./run
  1 ./proc
 46 ./dev
 65 ./bin
% 

When I create /etc in the tarball, I get further errors, about various
other dirents not existing: /etc/apt/apt.conf.d/, /root, /bin/bash,
even /bin/sh.

By comparison, the (working) jessie chroot has:

% tar tf jessie.tar.gz | cut -d/ -f 1,2 | uniq -c | sort -n
⋮
 82 ./sbin
103 ./bin
354 ./etc
607 ./lib
898 ./var
  10887 ./usr
% 

I created the sid chroot last Friday with «/usr/sbin/sbuild-createchroot
--include=eatmydata --make-sbuild-tarball=/path/to/unstable-amd64.tar.gz
unstable `mktemp -d` http://httpredir.debian.org/debian».  At the time
I used sbuild from stable (0.65.2-1).  I just now re-created that chroot
using sbuild 0.71.0-2 (locally rebuilt on jessie), and it now works.

I still don't know why the stable sbuild didn't work, though.  (Or
whether upgrading sbuild was the fix: perhaps something changed in the
archive since Friday.)  Should I file a bug about that?

Thanks,

Daniel

Bug#836903: RFS: qevercloud/3.0.2+ds-1 [ITP] -- Unofficial Evernote Cloud API library for Qt

2016-09-13 Thread Boyuan Yang 
Hello,

2016-09-12 21:34 GMT+08:00 Sean Whitton :
> Dear Boyuan,
>
> On Sun, Sep 11, 2016 at 08:48:15AM +0800, Boyuan Yang wrote:
>> > - status of lemon parser currently unclear
>>
>> This is fixed in the RFS of qevercloud before already. Of course we are
>> using the lemon parser from Debian. The bundled source code of lemon
>> is discarded in the source package. Sorry I didn't update the situation
>> on that Github thread, which is a little bit outdated.
>
> Great.
>
>> You suggested the separate packaging of qevercloudgenerator, but now we
>> seems to agree that since it is not useful for anything other than building
>> qevercloud,  it should not be packaged separately.
>
> Right.
>
>> Now the problem is focused on the separation of evernote-thrift files.
>>
>> I believe you suggested packaging thrift files alone, since the
>> separated package
>> can be used by other packages (most likely as a Build-Depend?), and to deal
>> with the FTBFS of qevercloud after the version bump of evernote-thrift, we 
>> can
>> include multiple copies. Did you suggest the coexistence of multiple versions
>> of evernote-thrift in the Debian repository, for example,
>> "evernote-thrift-1-25" and
>> "evernote-thrift-1-28"? Or if I misunderstood, it is just one package
>> "evernote-thrift"
>> but provides different versions of files inside one binary package (e.g.,
>> /usr/share/evernote/thrift/1.25/foobar and
>> /usr/share/evernote/thrift/1.28/foobar)?
>
> No, I was suggesting that you just embed the thrift files in your
> qevercloud source package, as you wanted to do originally.
>
> When I said "multiple versions in the archive" I meant copies in various
> source packages, but not in any binary packages.
>
>> Personally I am against the separated package of evernote-thrift, and
>> the main reason is that it is not useful; thrift files are technically
>> used by no one other than evernote people; developers are
>> encouraged/guided to use official Evernote SDK released by evernote,
>> which is already a generated project from the thrift files; no one
>> else is parsing thrift files by him/herself.
>
> Right.  They shouldn't be installed: just present in the qevernote
> source package for the purposes of regeneration.
>
> Could you confirm that your git repository is up-to-date with our
> discussion, so I can (finally!) do a review of your packaging, please?

Yes, they are up-to-date now. The package on debian-mentors is also
updated.


Sincerely,
Boyuan Yang

Bug#836381: RFS: couchapp/1.0.2+dfsg1-1

2016-09-13 Thread gustavo panizzo 
On Wed, Sep 14, 2016 at 11:00:55AM +0800, gustavo panizzo wrote:
> Please wait, I missed an update to debian/watch.

Now git repo is ready to be reviewed

--
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333

keybase: https://keybase.io/gfa


signature.asc
Description: PGP signature

Re: EFL/1.18, Enlightenment/0.21 updates

2016-09-13 Thread Paul Wise 
On Tue, 2016-09-13 at 21:11 -0400, Ross Vandegrift wrote:

> it was pointed out on pkg-e-devel that this breaks
>  links that contain the source package name:

I personally don't think that is important enough to keep using the
wrong name. The old name will continue to be available in the Debian
changelog file and people looking that far back in the history can use
the old source package name to look up old versions of the package.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#836381: RFS: couchapp/1.0.2+dfsg1-1

2016-09-13 Thread gustavo panizzo 
Please wait, I missed an update to debian/watch.

On Wed, Sep 14, 2016 at 10:55:40AM +0800, gustavo panizzo wrote:
> On Fri, Sep 09, 2016 at 07:26:52AM +, Gianfranco Costamagna wrote:
> > Hi
> > 
> > >ohhh, totally get it. thanks for spotting it
> > 
> > 
> > thanks for getting it ;)
> > 
> > is the only way i found to silence lintian about non-encrypted Vcs- urls
> > 
> > 
> > "https://anonscm.debian.org/cgit/collab-maint/couchapp.git;
> > 
> > and 
> > 
> > "https://anonscm.debian.org/git/collab-maint/couchapp.git;
> 
> both can be used on the browser or git clone, neither of them can be
> used to push :(
> 
> > 
> > simple as that :)
> > >i removed it as it was going to bit rot, i replaced it by README.source
> > >which sould make easier for others to follow.
> > 
> > "diferently." <-- typo
> 
> arrgghhh
> 
> > 
> > I still think Files-Excluded copyright feature is a better solution, but
> > feel free to use your best workflow :)
> > 
> > new review:
> > couchapp-1.0.2+dfsg1/debian/CHANGELOG
> > 
> > this file has been added in this upload...
> > mistake?
> its the upstream changelog, i generated it from git log
> 
> > 
> > 
> > still one license missing
> > ./couchapp/templates/vendor/couchapp/_attachments/md5.js
> > 
> > 
> > * A JavaScript implementation of the RSA Data Security, Inc. MD5 Message
> > * Digest Algorithm, as defined in RFC 1321.
> > * Version 2.1 Copyright (C) Paul Johnston 1999 - 2002.
> > * Other contributors: Greg Holt, Andrew Kepert, Ydnar, Lostinet
> > * Distributed under the BSD License
> > * See http://pajhome.org.uk/crypt/md5 for more info.
> > 
> ar, fixed. thanks
> 
> > 
> > we should be really good after this one :)
> > 
> > (sorry for being so pedantic!)
> 
> no worries, thanks for keeping pushing it
> 
> 
> --
> 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333
> 
> keybase: https://keybase.io/gfa



-- 
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333

keybase: https://keybase.io/gfa

Bug#836381: RFS: couchapp/1.0.2+dfsg1-1

2016-09-13 Thread gustavo panizzo 
On Fri, Sep 09, 2016 at 07:26:52AM +, Gianfranco Costamagna wrote:
> Hi
> 
> >ohhh, totally get it. thanks for spotting it
> 
> 
> thanks for getting it ;)
> 
> is the only way i found to silence lintian about non-encrypted Vcs- urls
> 
> 
> "https://anonscm.debian.org/cgit/collab-maint/couchapp.git;
> 
> and 
> 
> "https://anonscm.debian.org/git/collab-maint/couchapp.git;

both can be used on the browser or git clone, neither of them can be
used to push :(

> 
> simple as that :)
> >i removed it as it was going to bit rot, i replaced it by README.source
> >which sould make easier for others to follow.
> 
> "diferently." <-- typo

arrgghhh

> 
> I still think Files-Excluded copyright feature is a better solution, but
> feel free to use your best workflow :)
> 
> new review:
> couchapp-1.0.2+dfsg1/debian/CHANGELOG
> 
> this file has been added in this upload...
> mistake?
its the upstream changelog, i generated it from git log

> 
> 
> still one license missing
> ./couchapp/templates/vendor/couchapp/_attachments/md5.js
> 
> 
> * A JavaScript implementation of the RSA Data Security, Inc. MD5 Message
> * Digest Algorithm, as defined in RFC 1321.
> * Version 2.1 Copyright (C) Paul Johnston 1999 - 2002.
> * Other contributors: Greg Holt, Andrew Kepert, Ydnar, Lostinet
> * Distributed under the BSD License
> * See http://pajhome.org.uk/crypt/md5 for more info.
> 
ar, fixed. thanks

> 
> we should be really good after this one :)
> 
> (sorry for being so pedantic!)

no worries, thanks for keeping pushing it


--
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333

keybase: https://keybase.io/gfa


signature.asc
Description: PGP signature

Bug#837650: RFS: cf-python/1.3.1-1 [ITP]

2016-09-13 Thread Ben Finney 
On Wed, 2016-09-14 11:17 +1000, Ben Finney  wrote:
> Here are some comments I have for improving the packaging work:

Further:

* The source package should ideally not contain non-source forms of the
work.

  I see that there is a tree of generated documentation that is not the
  source form.

  Instead, the generated files should be removed from the Debian source
  file, and the documentation built from its source form at build time
  using upstream's build procedure for that.

  Similarly, any non-source forms should be removed and (if necessary)
  replaced with their corresponding source in a re-packaged upstream
  tarball. The Debian build should use upstream's build system for
  generating those files from their source form, and only install that
  result.

-- 
 \
  `\
_o__) Ben Finney

Bug#837650: RFS: cf-python/1.3.1-1 [ITP]

2016-09-13 Thread Ben Finney 
Howdy Klaus,

Thank you for working on this package.

Here are some comments I have for improving the packaging work:

* When removing code, just remove it. You are tracking the work in a
VCS, there is generally no reason to commit changes that comments out
lines of code.

  So, in ‘debian/patches/’, the
  ‘0001-Remove-check-for-python-version.patch’ and
  ‘0003-Patch-sphinx-config-to-avoid-network-access-and-add-.patch’
  changes (actually, the Git commits you used to generate those files)
  should not comment any code lines but instead remove those lines.

* Wow, hard-coding a man page in a Python string literal is a fragile
way to store the document.

  Have you discussed with upstream the feasibility of moving those to
  their own first-class source documents, and reading from there at run
  time? Python ‘pkg_resources’ has functionality to locate and read a
  file installed as part of the package.

* In ‘debian/copyright’, please don't obfuscate the email addresses of
copyright holders. It's a needless barrier to getting useable contact
information for legal purposes.

* Is there a good reason to omit the “Upstream-Maintainer” field in the
header of the ‘debian-copyright’ file? There seems to be an obvious
single maintainer contact for this code base.

* The ‘cf/etc/udunits/’ tree looks like a bundled third-party work. Per
Debian Policy §4.13, should this work not be packaged separately and
listed as a dependency?

* Can you include a ‘debian/README.source’ explaining how you collated
the various parts and changes you've made from the upstream source?

  In particular, the procedure for making ‘debian/*.1’ and
  ‘debian/test_file.nc’ should be described, along with rationales that
  can be later re-visited if upstream policies change.

-- 
 \
  `\
_o__) Ben Finney

Re: EFL/1.18, Enlightenment/0.21 updates

2016-09-13 Thread Ross Vandegrift 

On 09/12/2016 10:21 PM, Paul Wise wrote:

On Mon, Sep 12, 2016 at 1:35 AM, Ross Vandegrift wrote:


https://mentors.debian.net/debian/pool/main/e/e17/e17_0.21.2-1.dsc


I'd suggest renaming the source and binary packages to
'enlightenment', e17 was never the right choice of name.


I agree this would be nice.  But it was pointed out on pkg-e-devel that 
this breaks links that contain the source package name:

https://packages.qa.debian.org/e/e17.html

Ross

Re: EFL/1.18, Enlightenment/0.21 updates

2016-09-13 Thread Ross Vandegrift 

On 09/12/2016 05:49 AM, Gianfranco Costamagna wrote:

I won't test/review, unless you want it to be uploaded in Debian
(with an RFS bug), sorry!


That's cool - thanks for taking a look at my questions.


2) The previous maintainer hasn't been active, so my work is not in the
alioth pkg-e-devel repo.  I've left the Vcs-* fields pointing at the
official repo but I'm currently pushing to:
 https://github.com/rvandegrift/efl.git
 https://github.com/rvandegrift/e.git



did you try to join the team?
the maintainer has been pinged by MIA team, and said "will fix in one month"
"2016-08-24: willfix 1m"

so, in case he orphan the package, you might ask to maintain them
(or, since I cc'd him, maybe sponsor/review your work)


I've been in occasional contact with Albin, and hope he'll have a change 
to review & sponsor.  I just posted here in case anyone was interested 
and had feedback in the meantime (sorry if that's off topic!)



4) As of 1.18, the efl source package includes previously separate
source packages.  I don't know if anything special needs to be done in



this situation.


I don't know, how do they evolve? all together or separately?


Upstream has opted to merge the source packages together to ease 
building and distribution.  Didn't see a benefit to reversing that.


I meant: is there anything extra a good source package should do when it 
absorbs another?



Thanks for any comments/suggestions,



sorry for providing almost none :)


Still managed to be useful :)

Ross

Re: schroot: 20copyfiles: cp: cannot create regular file '.../etc/resolv.conf'

2016-09-13 Thread Sean Whitton 
Dear Daniel,

Does etc exist in /srv/chroot/unstable-amd64 (or wherever you have the
base chroot)?

-- 
Sean Whitton

Solicitud de Información

2016-09-13 Thread Gerencia Comercial 
Estimados Srs.



Quisieramos entrar en contacto con la persona encarga de compras de
servicios de Transporte de Carga de su organización, nos gustaría ofrecerles 
nuestros servicios, por lo que agradecemos cualquier información que nos pueda 
facilitar de contacto de la misma.

Puede ver nuestra nueva presentación comercial [1] DESCARGAR

Reciban un cordial saludo, quedo a la espera de sus comentarios,
Atentamente,

Luis Arriaga
Gerente Comercial
[2] ven...@transmaquina.com.ve
0424-1361299

[3] www.transmaquina.com.ve

This message was sent to t...@test.com by Gerencia Comercial
Caracas

Unsubscribe| Manage Subscription| Forward Email| Report Abuse


 References:

1. 
http://attachment.benchmarkemail.com/c464851/TransMaquina-Presentación-Comercial-2016.pdf
2. mailto:ven...@transmaquina.com.ve
3. 
http://benchemail.bmetrack.com/c/l?u=5F05768=8EA96C=717D3=1=3hZXdo9tE%2FWpG1lt0VIgVKHLBhtVN81S79F%2FXN9Dq84%3D=1


This message was sent to debian-mentors@lists.debian.org by 
vent...@transmaquina.com.ve

You can modify/update your subscription via the link below.

Unsubscribe from all mailings
http://benchemail.bmetrack.com/c/su?e=9FFE9C=717D3=F60F9B9=5OxzrBLumxPynvuzaF1bp7%2FeNWSbTFLphENb71UYrR8%3D=A0B1112


Manage Subscription
http://benchemail.bmetrack.com/c/s?e=9FFE9C=717D3=F60F9B9=5OxzrBLumxPynvuzaF1bp7%2FeNWSbTFLphENb71UYrR8%3D=A0B1112


Forward Email
http://benchemail.bmetrack.com/c/f?e=9FFE9C=717D3=F60F9B9=5OxzrBLumxPynvuzaF1bp7%2FeNWSbTFLphENb71UYrR8%3D=A0B1112


Report Abuse
http://benchemail.bmetrack.com/Abuse?e=9FFE9C=717D3=F60F9B9=5OxzrBLumxPynvuzaF1bp7%2FeNWSbTFLphENb71UYrR8%3D=A0B1112


Caracas

Email Marketing
BenchmarkEmail.com
 [http://benchemail.bmetrack.com]

Bug#837609: RFS: budgie-desktop/10.2.7-1

2016-09-13 Thread foss.freedom 
Hi Gianfranco,

  many thanks for reviewing this revised package.

(I'll make sure I use "plain text mode" for gmail from now on)

1. I've completely redone the copyright file - obviously alot of the
files Ikey has updated to 2016 (but not all) so this is reflected in
the new copyright + a couple of double copyrighters such as Josh Klar.

I ran licensecheck as well - where the files where marked as
"generated" and did not have a .vala equivalent I have not added these
to the copyright.  These are by-products of the make distcheck process
upstream uses.

2. I re-raised the generated files question here upstream:

https://github.com/solus-project/budgie-desktop/issues/588

"
I seem to remember we had this conversation before, getting deja vu
anyway :) That's how the Vala+autotools stuff works. The only way for
me to workaround it is to forcibly delete the stamps, which in turn
breaks distcheck. We don't use any conditionals in the Vala code for
exactly this reason, we know the .c files aren't being regenerated, so
the conditionals would never work (they don't make it to the .c..)

We could try to hack the .c's out it, but I think the time would be
best spent on rewriting to C for 10.3, as we need to fix all those odd
issues (like not being able to have proper relro plugins), then we can
just drop all the .vala anyway. I'd like to see what Debian makes of
that proposition, because I think we're all a bit sick of Vala in
Budgie Desktop by now anyway, right? :)"

3. I've added the libaccountservice-dev to the changelog.

I've also rerun check-all-the-things and this looks similar to the
results of budgie-desktop-10.2.6

Cheers

David

On 13 September 2016 at 10:57, Gianfranco Costamagna
 wrote:
> control: owner -1 !
> control: tags -1 moreinfo
>
> Hi,(please don't use html in mail, when possible)
>
>
>>budgie-desktop:
>
> 1) lots of missing copyrights, e.g.
> Copyright (C) 2015-2016 Solus Project
>
> Copyright 2014 Josh Klar  (original Budgie work, prior to 
> Budgie 10)
>
> 2) I see a lot of autogenerated files:
>
> "/* main.c generated by valac 0.32.1, the Vala compiler"
>
> are you sure you are rebuilding them in Debian builds?
>
> grep generated . -Ri |grep vala |grep -v "do not" |wc -l
> 57
>
> 3) added dependency not mentioned in changelog
> + libaccountsservice-dev,
>
> other stuff seems good
>
> G.

Bug#837704: RFS: usbguard/0.5.14+ds1-2

2016-09-13 Thread Muri Nicanor 
Package: sponsorship-requests
Severity: normal

Dear mentors,

because there is still some stuff to sort out with the new usbguard 0.6
release, i fixed the bugs in the already uploaded release and made a new
debian revision. I hope that approach is oke.

I am looking for a sponsor for my package "usbguard"

 * Package name: usbguard
   Version : 0.5.14+ds1-2
   Upstream Author : Daniel Kopeček 
 * URL : https://github.com/dkopecek/usbguard
 * License : GPL-2+
   Section : utils

  It builds those binary packages:

 libusbguard-dev - USB device authorization policy framework -
development files
 libusbguard0 - USB device authorization policy framework - shared library
 usbguard   - USB device authorization policy framework
 usbguard-applet-qt - USB device authorization policy framework - qt applet

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/usbguard


Alternatively, one can download the package with dget using this command:

dget -x
https://mentors.debian.net/debian/pool/main/u/usbguard/usbguard_0.5.14+ds1-2.dsc

More information about usbguard can be obtained from
https://dkopecek.github.io/usbguard/

  Changes since the last upload:

  * d/control:
   - Add systemd to build dependencies (Closes: #836713)
   - Change architectures to linux-any in d/control
  * d/rules
   - Add sysconfdir flag to autoconf (Closes: #837176)
  * d/patches/
   - Fix mips build (Closes: #836712)
   - Set correct IPCAllowedGroups (Closes: #837175)

cheers,
-- 
muri




signature.asc
Description: OpenPGP digital signature

Bug#832429: marked as done (RFS: hydroffice.bag/0.2.15-1 [ITP])

2016-09-13 Thread Debian Bug Tracking System 
Your message dated Tue, 13 Sep 2016 18:35:45 +0100
with message-id <1473788145.5145.3.ca...@gmail.com>
and subject line 
has caused the Debian Bug report #832429,
regarding RFS: hydroffice.bag/0.2.15-1 [ITP]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
832429: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832429
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "python-hydroffice.bag"

* Package name: python-hydroffice.bag
  Version : 0.2.15-1
  Upstream Author : Brian R. Calder and Giuseppe Masetti
* URL : http://www.hydroffice.org
* License : LGPL-3
  Section : science

It builds those binary packages:

  hydroffice.bag-tools - tools for hydroffice.bag
  python-hydroffice.bag - manage Bathymetric Attributed Grid (BAG) data 
files in Python 2

  python-hydroffice.bag-doc - documentation for hydroffice.bag
  python3-hydroffice.bag - manage Bathymetric Attributed Grid (BAG) 
data files in Python 3


To access further information about this package, please visit the 
following URL:


  https://mentors.debian.net/package/python-hydroffice.bag

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/p/python-hydroffice.bag/python-hydroffice.bag_0.2.15-1.dsc


Successful build on debomatic:


http://debomatic-amd64.debian.net/distribution#unstable/python-hydroffice.bag/0.2.15-1/buildlog

Changes since the last upload:

   * Initial release. (Closes: #823233)

Regards,
Ghislain Vaillant
--- End Message ---
--- Begin Message ---
uploaded to unstable--- End Message ---

update .preinst file

2016-09-13 Thread Herbert Fortes 
Hi,


I have to update 4 debian/*.preinst files.


Right now the files are like here[0]:


|

if dpkg --compare-versions "$2" lt "1.2.4+dfsg1-7" ; then
   rm -rf /usr/share/doc/bogofilter || true
fi [0] -
https://anonscm.debian.org/git/collab-maint/bogofilter.git/tree/debian/bogofilter.preinst
This approach has problems on an upgrade from Jessie to Stretch[1].The
recommendation today is to use 'dpkg-maintscript-helper', so I should
change to ("a real directory is switched to a symlink"): [1] -
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832291 if
dpkg-maintscript-helper supports dir_to_symlink 2>/dev/null; then
dpkg-maintscript-helper dir_to_symlink \ /usr/share/doc/bogofilter
bogofilter 1.2.4+dfsg1-8 bogofilter -- "$@" fi From the manpage:
"pathname(/usr/share/doc/bogofilter here) is the absolute name of the
old directory (the path will be a symlink at the end of the
installation) and new-target (bogofilter here) is the target of the new
symlink at pathname. It can either be absolute or relative to the
directory containing pathname." But the symlink is created by
dh_installdocs[1] already. I just want to remove the directory. [1] -
'dh_installdocs --link-doc=bogofilter-common' The manpage again:
COMMANDS AND PARAMETERS supports command rm_conffile conffile
[prior-version [package]] mv_conffile old-conffile new-conffile
[prior-version [package]] symlink_to_dir pathname old-target
[prior-version [package]] dir_to_symlink pathname new-target
[prior-version [package]] What should I do ? Regards, Herbert

|

Re: FTBFS: how to test fixes

2016-09-13 Thread 殷啟聰 
Hi Muri,

With qemu-user-static binfmt-support and debootstrap you can establish
a Debian root filesystem of any architecture supported by QEMU. Then
you chroot into the directory and you basically entered a
not-so-perfect virtual environment. You can test yout packages there.

By following the instructions at 
you can get what you want.

Cheers,
Kai-Chung Yan

2016-09-06 1:07 GMT+08:00 Muri Nicanor :
> hi,
>
> so, i've got my first two FTBFS bugs (on mips and hppa)- what the
> recommended way of testing fixes for architectures i don't have
> testmachines of?
>
> cheers,
> --
> muri
>



-- 
/*
* 殷啟聰 | Kai-Chung Yan
* 一生只向真理與妻子低頭
* Undergraduate student in National Taichung University of Education
* LinkedIn: 
* Blog: 
*/

Bug#836215: RFS: phalanx/25-1 [ITA]

2016-09-13 Thread Jose G. López 
Hi Gianfranco,

Thanks for reviwing! I must say I've addressed most of your points but
testing the new version (25), I've found that it doesn't work as
expected in Scid. Scid has a feature to play versus Phalanx (tactical
game) but it needs a special version. The package in sid works well
while new version only works if you choose the option to play
a specific opening.

Apart from that, the engine works well both in scid
(analyzing) and xboard (analyzing and playing with). I've tried to
figure out the changes done to phalanx-scid engine but I don't come by
with a solution.

So don't know if it's better to fix and improve the version in
sid (22+d051004) while asking Scid upstream to import the new version
of Phalanx and knowing what changes need to be tweaked.

What do you think?

Regards,


pgp3RgkkHVa86.pgp
Description: PGP signature

Bug#837650: RFS: cf-python/1.3.1-1 [ITP]

2016-09-13 Thread Klaus Zimmermann 
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "cf-python"

* Package name: cf-python
  Version : 1.3.1-1
  Upstream Author : David Hassell 
* URL : http://cfpython.bitbucket.org/
* License : Expat
  Section : python

It builds those binary packages:

   python-cf  - Python processing of Climate and Forecast (CF) data models 
(Python 2)
python-cf-doc - Python processing of Climate and Forecast (CF) data models 
(Documentation)

To access further information about this package, please visit the following 
URL:

https://mentors.debian.net/package/cf-python

Alternatively, one can download the package with dget using this command:

 dget -x 
https://mentors.debian.net/debian/pool/main/c/cf-python/cf-python_1.3.1-1.dsc

More information about hello can be obtained from https://www.example.com.

Changes since the last upload:

  cf-python (1.3.1-1) UNRELEASED; urgency=medium

  * Initial release (Closes: #777315)

 -- Klaus Zimmermann   Fri, 09 Sep 2016 17:31:55 +0200


Regards,
 Klaus Zimmermann

Bug#837609: RFS: budgie-desktop/10.2.7-1

2016-09-13 Thread Gianfranco Costamagna 
control: owner -1 !
control: tags -1 moreinfo

Hi,(please don't use html in mail, when possible)


>budgie-desktop:

1) lots of missing copyrights, e.g.
Copyright (C) 2015-2016 Solus Project

Copyright 2014 Josh Klar  (original Budgie work, prior to 
Budgie 10)

2) I see a lot of autogenerated files:

"/* main.c generated by valac 0.32.1, the Vala compiler"

are you sure you are rebuilding them in Debian builds?

grep generated . -Ri |grep vala |grep -v "do not" |wc -l
57

3) added dependency not mentioned in changelog
+ libaccountsservice-dev,

other stuff seems good

G.