Re: Request for access to porterbox

[Adam Borowski]

On Thu, Jul 28, 2016 at 12:56:11AM +0200, Christian Seiler wrote:
> On 07/28/2016 12:21 AM, Adam Borowski wrote:
> > On Wed, Jul 27, 2016 at 11:07:17PM +0200, Christian Seiler wrote:
> >> m68k and sh4 do work in qmeu-user-static chroots, the setup
> >> is not quite as trivial however. (I can give you a tarball
> >> that will work in pbuilder and schroot though.)
> > 
> > For qemu-user for sh4 it's:
> > 
> > CHROOT=/srv/chroots/sh4   #name the chroot here
> > apt-get -y install debian-ports-archive-keyring qemu-user-static
> > btrfs subv create "$CHROOT" || mkdir "$CHROOT"
> > mkdir -p "$CHROOT/usr/bin"
> > cp -p /usr/bin/qemu-sh4-static "$CHROOT/usr/bin/"
> > debootstrap --arch=sh4 \
> > --keyring=/usr/share/keyrings/debian-ports-archive-keyring.gpg \
> > unstable "$CHROOT" http://ftp.ports.debian.org/debian-ports/
> 
> That works now? When I set up a SH4 chroot a while back, I had to
> use the qemu-sh4-static binary from the i386 version of the
> qemu-user-static package, because the amd64 version was broken.
> (Luckily, static linking.)

#805827 which is an ex-bug.

> qemu-debootstrap fails for m68k with Illegal Instruction at the
> beginning of debootstrap --second-stage. I did get a working
> chroot by fiddling with stuff for a while manually IIRC (not on
> the computer I'm currently on, I'd have to look that up), but I
> don't remember what I did.

I could swear this worked at some point.  I guess the instruction set was
bumped recently.

> Actually, I remember now: you need to compile a custom version of
> qemu-m68k-static because upstream QEMU doesn't support the CPUs
> that Debian's port requires. It's even described on the Debian
> Wiki, see:
> https://wiki.debian.org/M68k/sbuildQEMU

Ie, "you need to get qemu with patches not yet merged upstream", a common
story (like other bugs mentioned).

> Plus, aptitude is broken on many (but not all) archs when used
> together with qemu-user-static (segfaults), so if you use that
> kind of chroot together with pbuilder, in my experience you need
> to revert to the classic satisfydepends (which is much slower)
> to make pbuilder work properly.

As debootstrap uses regular apt rather than aptitude, why would this be a
concern?  And aptitude's dependency resolution is broken more often than
not, so sticking with apt is more reliable also on the installed system.

> Also, if you have debian-ports for the binary packages, you still
> need the normal archive for the source packages, so the deb and
> deb-src lines (if you want to add both to sources.list) diverge.

debootstrap doesn't have a way to use two archives, so this is something to
be configured once the chroot is installed.

> > Same works for all other archs supported by qemu, other than powerpcspe
> > (needs QEMU_CPU=e500v2).
> 
> mips64el needs QEMU_CPU=mips64dspr2. (Most stuff works without
> that env var, but some things don't.)

gcc recently bumped to R2 ISA in 5.2.1-17.

> ppc64el needs QEMU_CPU=POWER8. (qemu-static-ppc64 and -ppc64el
> are basically the same save for endianness, but Debian's pp64el
> port requires a POWER8 CPU at least, whereas the ppc64 port runs
> on POWER5 and higher IIRC.)

#813698, an ex bug.

> I have never gotten sparc64 to work in qemu-user-static, that I
> only got working with qemu-system. (Debian Wiki contains some
> instructions for that though.)

Aye.

-- 
An imaginary friend squared is a real enemy.

Re: [RFS] I need an sponsor for 2 Go packages

[Gianfranco Costamagna]

Hi,


>PS: can I ping you when I have the new asciinema package?


I'm not a go developer, so somebody from your team might be better suitable
to look at the packages, but you can count on me as a backup sponsor.
(BTW go seems a really nice and funny language, so I might learn it one day)


and if the package becomes Python again... even better, I can do it

G.

Re: Request for access to porterbox

[Gianfranco Costamagna]

Hi,




>Plus, aptitude is broken on many (but not all) archs when used
>together with qemu-user-static (segfaults), so if you use that
>kind of chroot together with pbuilder, in my experience you need
>to revert to the classic satisfydepends (which is much slower)
>to make pbuilder work properly.


I also have this annoying problem, when trying to use arm64 and x86 archs
I always have to switch back the configuration file, and right now
I ended up in using the slower classic resolver.

Do you plan to report a bug? AFAIR this happened around apt 1.2, but
I never digged into the issue, nor debugged it.


G.

Bug#832647: marked as done (RFS: caffe/1.0.0~rc3-4)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jul 2016 06:19:55 + (UTC)
with message-id 
<1270172435.10225066.1469686795170.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#832647: RFS: caffe/1.0.0~rc3-4
has caused the Debian Bug report #832647,
regarding RFS: caffe/1.0.0~rc3-4
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.)


-- 
832647: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal

  Dear mentors,

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

 * Package name: caffe
   Version : 1.0.0~rc3-4
   Upstream Author : BVLC
 * URL : caffe.berkeleyvision.org
 * License : BSD-2-Clause
   Section : science

  It builds those binary packages:

caffe-cpu  - Fast, open framework for Deep Learning (Meta)
 caffe-doc  - Doxygen Document of Caffe
 caffe-tools-cpu - Tools for fast, open framework for Deep Learning
(CPU_ONLY)
 libcaffe-cpu-dev - development files for Caffe (CPU_ONLY)
 libcaffe-cpu1 - library of Caffe, deep learning framework (CPU_ONLY)
 python3-caffe-cpu - Python3 interface of Caffe (CPU_ONLY)

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

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


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

dget -x
https://mentors.debian.net/debian/pool/main/c/caffe/caffe_1.0.0~rc3-4.dsc


  Changes since the last upload:


  * Cherry-pick upstream fixes for map size issue.
- dont-set-map-size-1TB-in-db-lmdb
- print-to-stderr-for-example-LMDB-code
- update-MNIST-example-to-use-new-DB-classes
  * Update symbols control file, diverge symbols control file for ppc64el.
  * Synchronize packaging with src:caffe-contrib (= 1.0.0~rc3-2).



-- 
Best,
Lumin
--- End Message ---
--- Begin Message ---
Hi

>  I am looking for a sponsor for my package "caffe"


done.

G.--- End Message ---

Bug#832647: RFS: caffe/1.0.0~rc3-4

[Lumin]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

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

 * Package name: caffe
   Version : 1.0.0~rc3-4
   Upstream Author : BVLC
 * URL : caffe.berkeleyvision.org
 * License : BSD-2-Clause
   Section : science

  It builds those binary packages:

caffe-cpu  - Fast, open framework for Deep Learning (Meta)
 caffe-doc  - Doxygen Document of Caffe
 caffe-tools-cpu - Tools for fast, open framework for Deep Learning
(CPU_ONLY)
 libcaffe-cpu-dev - development files for Caffe (CPU_ONLY)
 libcaffe-cpu1 - library of Caffe, deep learning framework (CPU_ONLY)
 python3-caffe-cpu - Python3 interface of Caffe (CPU_ONLY)

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

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


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

dget -x
https://mentors.debian.net/debian/pool/main/c/caffe/caffe_1.0.0~rc3-4.dsc


  Changes since the last upload:


  * Cherry-pick upstream fixes for map size issue.
- dont-set-map-size-1TB-in-db-lmdb
- print-to-stderr-for-example-LMDB-code
- update-MNIST-example-to-use-new-DB-classes
  * Update symbols control file, diverge symbols control file for ppc64el.
  * Synchronize packaging with src:caffe-contrib (= 1.0.0~rc3-2).



-- 
Best,
Lumin

Re: Request for access to porterbox

[Paul Wise]

On Thu, Jul 28, 2016 at 6:21 AM, Adam Borowski wrote:

> CHROOT=/srv/chroots/sh4   #name the chroot here
> apt-get -y install debian-ports-archive-keyring qemu-user-static
> btrfs subv create "$CHROOT" || mkdir "$CHROOT"
> mkdir -p "$CHROOT/usr/bin"
> cp -p /usr/bin/qemu-sh4-static "$CHROOT/usr/bin/"
> debootstrap --arch=sh4 \
> --keyring=/usr/share/keyrings/debian-ports-archive-keyring.gpg \
> unstable "$CHROOT" http://ftp.ports.debian.org/debian-ports/

BTW, you can use qemu-debootstrap from the qemu-user-static package to
simplify this command.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Re: [RFS] I need an sponsor for 2 Go packages

[gustavo panizzo (gfa)]

On Wed, Jul 27, 2016 at 05:13:16PM +, Gianfranco Costamagna wrote:
> Hi,
> 

Gianfranco

Upstream went back to Python, so I won't upload this version or its needed 
dependency, i
if you are interested in golang-github-creack-termios, you can take the package 
from alioth, its
ready IMHO, only 3 lintian warnings

- debian-watch-may-check-gpg-signature
  upstream doesn't do releases, I placed a debian/watch file
  in place in case they start doing them.
 
- no-upstream-changelog
  upstream doesn't keep a changelog
 
- extended-description-is-probably-too-short
  upstream readme.md file is
  only 1 sentence, this pkg is an small library there is not much to say
  about it

thanks for your time, I apologize for the change of plans.

PS: can I ping you when I have the new asciinema package?

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

keybase: http://keybase.io/gfa


signature.asc
Description: PGP signature

Re: [RFS] I need an sponsor for 2 Go packages

[gustavo panizzo (gfa)]

On Thu, Jul 28, 2016 at 02:04:02AM +0200, Daniele Tricoli wrote:
> Hello Gustavo,
> 
> On Wednesday, July 27, 2016 03:17:29 PM gustavo panizzo wrote:
> > I'm the maintainer of asciinema, a while ago upstream decided to rewrite
> > it in Go, previously it was a Python app.
> 
> It seems upstream went back to Python:
> http://blog.asciinema.org/post/and-now-for-something-completely-different/
:-O

> 
> I think it is better to update to 1.3, and skip the Go release.
I will do that, what a waste of time!.

thanks for the catch, I had the package ready for some time, I didn't
check their blog




> 
> Kind regards,
> 
> -- 
>  Daniele Tricoli 'eriol'
>  https://mornie.org



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

keybase: http://keybase.io/gfa


signature.asc
Description: PGP signature

Re: [RFS] I need an sponsor for 2 Go packages

[Daniele Tricoli]

Hello Gustavo,

On Wednesday, July 27, 2016 03:17:29 PM gustavo panizzo wrote:
> I'm the maintainer of asciinema, a while ago upstream decided to rewrite
> it in Go, previously it was a Python app.

It seems upstream went back to Python:
http://blog.asciinema.org/post/and-now-for-something-completely-different/

I think it is better to update to 1.3, and skip the Go release.

Kind regards,

-- 
 Daniele Tricoli 'eriol'
 https://mornie.org

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

Re: Request for access to porterbox

[Christian Seiler]

On 07/28/2016 12:56 AM, Christian Seiler wrote:
> qemu-debootstrap fails for m68k with Illegal Instruction at the
> beginning of debootstrap --second-stage. I did get a working
> chroot by fiddling with stuff for a while manually IIRC (not on
> the computer I'm currently on, I'd have to look that up), but I
> don't remember what I did.

Actually, I remember now: you need to compile a custom version of
qemu-m68k-static because upstream QEMU doesn't support the CPUs
that Debian's port requires. It's even described on the Debian
Wiki, see:
https://wiki.debian.org/M68k/sbuildQEMU

Regards,
Christian

Re: Request for access to porterbox

[Christian Seiler]

On 07/28/2016 12:21 AM, Adam Borowski wrote:
> On Wed, Jul 27, 2016 at 11:07:17PM +0200, Christian Seiler wrote:
>> m68k and sh4 do work in qmeu-user-static chroots, the setup
>> is not quite as trivial however. (I can give you a tarball
>> that will work in pbuilder and schroot though.)
> 
> For qemu-user for sh4 it's:
> 
> CHROOT=/srv/chroots/sh4   #name the chroot here
> apt-get -y install debian-ports-archive-keyring qemu-user-static
> btrfs subv create "$CHROOT" || mkdir "$CHROOT"
> mkdir -p "$CHROOT/usr/bin"
> cp -p /usr/bin/qemu-sh4-static "$CHROOT/usr/bin/"
> debootstrap --arch=sh4 \
> --keyring=/usr/share/keyrings/debian-ports-archive-keyring.gpg \
> unstable "$CHROOT" http://ftp.ports.debian.org/debian-ports/

That works now? When I set up a SH4 chroot a while back, I had to
use the qemu-sh4-static binary from the i386 version of the
qemu-user-static package, because the amd64 version was broken.
(Luckily, static linking.)

qemu-debootstrap fails for m68k with Illegal Instruction at the
beginning of debootstrap --second-stage. I did get a working
chroot by fiddling with stuff for a while manually IIRC (not on
the computer I'm currently on, I'd have to look that up), but I
don't remember what I did.

Plus, aptitude is broken on many (but not all) archs when used
together with qemu-user-static (segfaults), so if you use that
kind of chroot together with pbuilder, in my experience you need
to revert to the classic satisfydepends (which is much slower)
to make pbuilder work properly.

Also, if you have debian-ports for the binary packages, you still
need the normal archive for the source packages, so the deb and
deb-src lines (if you want to add both to sources.list) diverge.

> Same works for all other archs supported by qemu, other than powerpcspe
> (needs QEMU_CPU=e500v2).

mips64el needs QEMU_CPU=mips64dspr2. (Most stuff works without
that env var, but some things don't.)

ppc64el needs QEMU_CPU=POWER8. (qemu-static-ppc64 and -ppc64el
are basically the same save for endianness, but Debian's pp64el
port requires a POWER8 CPU at least, whereas the ppc64 port runs
on POWER5 and higher IIRC.)

I have never gotten sparc64 to work in qemu-user-static, that I
only got working with qemu-system. (Debian Wiki contains some
instructions for that though.)

> Non-linux archs need qemu-system rather than qemu-user.  As all of them are
> x86, you want -enable-kvm, or, if you're scared by qemu-system, virtualbox.

I would always recommend libvirt + virt-manager for VMs (have
been using that since Squeeze, works *really* well, I have even
migrated running VMs between hosts since Squeeze with libvirt +
virsh, without any problems).

Regards,
Christian

Re: Request for access to porterbox

[Adam Borowski]

On Wed, Jul 27, 2016 at 11:07:17PM +0200, Christian Seiler wrote:
> m68k and sh4 do work in qmeu-user-static chroots, the setup
> is not quite as trivial however. (I can give you a tarball
> that will work in pbuilder and schroot though.)

No, that's wrong.  For these archs, qemu-user setup _is_ trivial. :)
It'd probably be helpful to gather such copypasta in one place, though:
wiki? a package?  It gets more complex for qemu-system, though -- only
some archs can do just "toss me a d-i ISO image and next/next/next".

For qemu-user for sh4 it's:

CHROOT=/srv/chroots/sh4   #name the chroot here
apt-get -y install debian-ports-archive-keyring qemu-user-static
btrfs subv create "$CHROOT" || mkdir "$CHROOT"
mkdir -p "$CHROOT/usr/bin"
cp -p /usr/bin/qemu-sh4-static "$CHROOT/usr/bin/"
debootstrap --arch=sh4 \
--keyring=/usr/share/keyrings/debian-ports-archive-keyring.gpg \
unstable "$CHROOT" http://ftp.ports.debian.org/debian-ports/

Same works for all other archs supported by qemu, other than powerpcspe
(needs QEMU_CPU=e500v2).  Obviously first-class archs will use the main
archive rather than debian-ports.  x32 needs support in host kernel.  hppa
is not supported by qemu (nor any other emulator).

Non-linux archs need qemu-system rather than qemu-user.  As all of them are
x86, you want -enable-kvm, or, if you're scared by qemu-system, virtualbox.


Meow!
-- 
An imaginary friend squared is a real enemy.

Re: dpkg-buildpackage: dpkg-source: no upstream tarball found

[James Cowgill]

Hi,

On Wed, 2016-07-27 at 23:16 +0200, chrishell wrote:
> Hello together,
> I have an issue with the new version of my package free42-nologo. I
> processed this the usual way: downloading, unpacking, debianize it
> with dh_make and making some changes with dquilt (makefile mainly). 

Since this is an update to an existing package, you don't need to re-
deianize it or run dh_make again. From within the packaging of the old
version, simply run 'uupdate -v  '.

See:
https://www.debian.org/doc/manuals/maint-guide/update.en.html#newupstream

> Then I invoked dpkg-buildpackage -rfakeroot -us -uc and here I got en
> error for the wrong archive format of upstream:
> 
> dpkg-source: error: can't build with source format '3.0 (quilt)': no
> upstream tarball found at
> ../free42-nologo_1.4.77.orig.tar.{bz2,gz,lzma,xz} no upstream tarball
> ...

The error message is still referencing the old version number. This
probably means you havn't added a new debian/changelog entry yet.

James

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

Re: dpkg-buildpackage: dpkg-source: no upstream tarball found

[Gianfranco Costamagna]

Hi,

>I have an issue with the new version of my package free42-nologo. I

>../free42-nologo_1.4.77.orig.tar.{bz2,gz,lzma,xz} no upstream tarball ...



pull-debian-source free42-nologo

or
dget -u 
http://http.debian.net/debian/pool/main/f/free42-nologo/free42-nologo_1.4.77-1.1.dsc

or click here [1] and download the orig tarball.


[1] https://packages.debian.org/source/unstable/free42-nologo

HTH

G.

dpkg-buildpackage: dpkg-source: no upstream tarball found

[chrishell]

Hello together,
I have an issue with the new version of my package free42-nologo. I
processed this the usual way: downloading, unpacking, debianize it with
dh_make and making some changes with dquilt (makefile mainly). Then I
invoked dpkg-buildpackage -rfakeroot -us -uc and here I got en error for
the wrong archive format of upstream:

dpkg-source: error: can't build with source format '3.0 (quilt)': no
upstream tarball found at
../free42-nologo_1.4.77.orig.tar.{bz2,gz,lzma,xz} no upstream tarball ...

I tried to circumvent this by unpacking the actual archive, and then
created a tarball an 'gzippd' it, but not even this helped here. Does
anybody have a clue, how to solve this?

Thank you in advance

Best Regards Christian

Re: Request for access to porterbox

[Christian Seiler]

On 07/27/2016 07:41 PM, Dmitry Bogatov wrote:
> Hello, I am looking for DD to sponsor my request for access a portbox
> to debug #832544, #832543.
> Architectures requested: hurd, m68k, sh4

If you have access to x86 hardware (as most people do), you can
run Hurd in a VM - no need for a porterbox.

See https://wiki.debian.org/Debian_GNU/Hurd at the very top
under "installation and testing". Caveat: IIRC virtio doesn't
work on Hurd, so you need to emulate an IDE disk drive plus
a non-virtio network adapter for that to work.

m68k and sh4 do work in qmeu-user-static chroots, the setup
is not quite as trivial however. (I can give you a tarball
that will work in pbuilder and schroot though.) Also, gdb
and strace in qemu-user chroots are non-trivial to use.
Ask me if you're interested.

Regards,
Christian

Re: systemd WantedBy= target changed - canonical way to clean up old .wants symlinks?

[Christian Seiler]

On 07/27/2016 10:21 PM, Patrick Schleizer wrote:
> Hi!
> 
> When changing a systemd WantedBy= target...
> 
> Is there a canonical way to clean up the old .wants symlinks?
> 
> These are not automatically removed on package upgrades. Considered a
> bug or feature? :)

Bug, I reported that a while back:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797108
Unfortunately, I lost track of that at some point...

*re-add to TODO list*

> rm_conffile?

Probably just rm -f in postinst (with version check).

Regards,
Christian

Re: Request for access to porterbox

[Christian Seiler]

On 07/27/2016 09:17 PM, Andrey Rahmatullin wrote:
> On Wed, Jul 27, 2016 at 08:41:51PM +0300, Dmitry Bogatov wrote:
>> Rationaly: reproduce #832544, #832543
> I wonder why these bugs are important and not wishlist.

Because they are FTBFS bugs on non-release archs and hence should
be of severity important? (Just as FTBFS on release archs are
considered "serious".) important doesn't block testing migration,
so it doesn't impede anything even if you have -ENOTIME to fix
it right now.

(Developers Reference explicitly states: "be kind to porters".
I consider severity: important for FTBFS to be part of that.)

The only case where I think wishlist is appropriate if you have
packages that explicitly declare a subset of architectures (e.g.
because they contain hand-crafted assembly code for each arch
or are a compiler or similar) instead of Arch: any.

Regards,
Christian

Bug#832402: marked as done (RFS: helm-projectile/0.14.0-1 -- Helm integration for Projectile)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jul 2016 22:38:55 +0200
with message-id <39e1bbfb-f7d3-225f-217a-d69931c96...@debian.org>
and subject line Re: Bug#832402: RFS: helm-projectile/0.14.0-1 -- Helm 
integration for Projectile
has caused the Debian Bug report #832402,
regarding RFS: helm-projectile/0.14.0-1 -- Helm integration for Projectile
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.)


-- 
832402: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832402
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for src:helm-projectile.  This was formerly
part of src:projectile, but upstream has split their work into three git
repositories and is making separate releases.  Since I think the new
split makes more sense, I'm splitting the Debian package into three
source packages.

Since the binary package is already in Debian, I did not file an ITP.

* Package name: helm-projectile
  Version : 0.14.0-1
  Upstream Author : Bozhidar Batsov 
* URL : https://github.com/bbatsov/helm-projectile
* License : GPL-3+
  Section : lisp

Changes sinces the last upload:

  * Initial release (new source package split from src:projectile).

Download with dget:

dget -x 
http://mentors.debian.net/debian/pool/main/p/helm-projectile/helm-projectile_0.14.0-1.dsc

Or build it with gbp:

gbp clone --pristine-tar 
https://anonscm.debian.org/git/pkg-emacsen/pkg/helm-projectile
git checkout debian/0.14.0-1
git verify-tag debian/0.14.0-1 # if you have my key
gbp buildpackage

Thanks.

Sean Whitton


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Sun, 24 Jul 2016 20:07:15 -0700 Sean Whitton  
wrote:
> On Sun, Jul 24, 2016 at 07:57:36PM -0700, Sean Whitton wrote:
> > Or build it with gbp:
> > 
> > gbp clone --pristine-tar 
> > https://anonscm.debian.org/git/pkg-emacsen/pkg/helm-projectile
> > git checkout debian/0.14.0-1
> > git verify-tag debian/0.14.0-1 # if you have my key
> > gbp buildpackage
> 
> This tag does not actually exist yet (pkg-emacsen team policy for
> packages not yet uploaded).
> 
> HEAD should be: 5a9585376183e3e72131c757ae8da1f9540af1f4
> 

taken from mentors
BTW
>http://mentors.debian.net/debian/pool/main/p/helm-projectile/helm-projectile_0.14.0-1.dsc

ELINK!

in deferred/1

cheers,

G.



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#832403: marked as done (RFS: persp-projectile/1:0.2.0-1 -- integrate perspective.el with projectile)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jul 2016 22:34:47 +0200
with message-id <594fe855-d73f-f182-46b6-fe06db740...@debian.org>
and subject line RFS: persp-projectile/1:0.2.0-1 -- integrate perspective.el 
with projectile
has caused the Debian Bug report #832403,
regarding RFS: persp-projectile/1:0.2.0-1 -- integrate perspective.el with 
projectile
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.)


-- 
832403: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for src:persp-projectile.  This was formerly
part of src:projectile, but upstream has split their work into three git
repositories and is making separate releases.  Since I think the new
split makes more sense, I'm splitting the Debian package into three
source packages.

Since the binary package is already in Debian, I did not file an ITP.

I prepended an epoch to the version number so that this package can be
upgraded to from the old binary package elpa-persp-projectile:0.13.0-1.

* Package name: persp-projectile
  Version : 1:0.2.0-1
  Upstream Author : Daniel Wu and Bozhidar Batsov
* URL : https://github.com/bbatsov/persp-projectile
* License : GPL-3+
  Section : lisp

Changes sinces the last upload:

  * Initial release (new source package split from src:projectile).
  * Add epoch because previous binary package version was 0.13.0-1.

Download with dget:

dget -x 
http://mentors.debian.net/debian/pool/main/p/persp-projectile/persp-projectile_0.2.0-1.dsc

Or build it with gbp:

gbp clone --pristine-tar 
https://anonscm.debian.org/git/pkg-emacsen/pkg/persp-projectile
# head should be: 3b169889428a3c51b2faae4035916d5493cb06cd
gbp buildpackage

Thanks.

Sean Whitton


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
sponsored.

g.



signature.asc
Description: OpenPGP digital signature
--- End Message ---

systemd WantedBy= target changed - canonical way to clean up old .wants symlinks?

[Patrick Schleizer]

Hi!

When changing a systemd WantedBy= target...

Is there a canonical way to clean up the old .wants symlinks?

These are not automatically removed on package upgrades. Considered a
bug or feature? :)

rm_conffile?

Cheers,
Patrick

Re: Request for access to porterbox

[Jakub Wilk]

* Dmitry Bogatov , 2016-07-27, 22:04:

Clear-signed information, required by DSA team is attached.

[...]

Architectures requested: hurd, m68k, sh4
FWIW, the are currently no DSA-operated porterboxes for any of these 
architectures.
Is it true? According to https://db.debian.org/machines.cgi there is 
hurd and sh4 porterboxes.


Hurd porterbox does exist, but it's not operated by DSA.

I couldn't connect to any of the listed sh4 porterbox, but they're not 
operated by DSA either.



Rationaly: reproduce #832544, #832543

Have you asked on porters' mailing lists for help?

I found neither m68k nor sh4 lists


debian-68k@
debian-superh@

--
Jakub Wilk

Re: Request for access to porterbox

[Dmitry Bogatov]

> > > FWIW, the are currently no DSA-operated porterboxes for any of these
> > > architectures.
> > Is it true? According to https://db.debian.org/machines.cgi there is
> > hurd and sh4 porterboxes.
> And according to that page they are not DSA-operated.

You are right. I am going to write to debian-hurd, and where should I ask for
help about sh4 and m68k machines?

-- 
Accept: text/plain, text/x-diff
Accept-Language: eo,en,ru
X-Web-Site: sinsekvu.github.io

Re: Request for access to porterbox

[Andrey Rahmatullin]

On Wed, Jul 27, 2016 at 08:41:51PM +0300, Dmitry Bogatov wrote:
> Architectures requested: hurd, m68k, sh4
Note that those are not release arches.

> Rationaly: reproduce #832544, #832543
I wonder why these bugs are important and not wishlist.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Re: Request for access to porterbox

[Andrey Rahmatullin]

On Wed, Jul 27, 2016 at 10:04:23PM +0300, Dmitry Bogatov wrote:
> > FWIW, the are currently no DSA-operated porterboxes for any of these
> > architectures.
> Is it true? According to https://db.debian.org/machines.cgi there is
> hurd and sh4 porterboxes.
And according to that page they are not DSA-operated.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Re: Request for access to porterbox

[Dmitry Bogatov]

[2016-07-27 20:17] Jakub Wilk 
>
> * Dmitry Bogatov , 2016-07-27, 20:41:
> >Clear-signed information, required by DSA team is attached.
> [...]
> >Architectures requested: hurd, m68k, sh4
>
> FWIW, the are currently no DSA-operated porterboxes for any of these
> architectures.

Is it true? According to https://db.debian.org/machines.cgi there is
hurd and sh4 porterboxes.

> >Rationaly: reproduce #832544, #832543
> Have you asked on porters' mailing lists for help?

I found neither m68k nor sh4 lists, and did not asked on hurd one yet.

-- 
Accept: text/plain, text/x-diff
Accept-Language: eo,en,ru
X-Web-Site: sinsekvu.github.io

Bug#777651: closing RFS: syncterm/1.0+dfsg-1 [ITP] -- BBS terminal program from Synchronet

[Fernando Toledo]

El 26/07/16 a las 12:31, Gianfranco Costamagna escribió:
> control: reopen -1
> control: unarchive -1
> control: owner -1 jgoer...@complete.org
> 
> On Tue, 26 Jul 2016 04:33:09 + Bart Martens  
> wrote:
>> Package syncterm has been removed from mentors.
> 
> lets try to cc everybody :)
> 
> thanks
> 
> G.
>
Thanks!

I just upload again to mentors. I still search for sponsor

Saludos!

-- 
Fernando Toledo
Dock Sud BBS
http://bbs.docksud.com.ar
telnet://bbs.docksud.com.ar

Re: Request for access to porterbox

[Jakub Wilk]

* Dmitry Bogatov , 2016-07-27, 20:41:

Clear-signed information, required by DSA team is attached.

[...]

Architectures requested: hurd, m68k, sh4


FWIW, the are currently no DSA-operated porterboxes for any of these 
architectures.



Rationaly: reproduce #832544, #832543


Have you asked on porters' mailing lists for help?

--
Jakub Wilk

Re: Request for access to porterbox

[Dmitry Bogatov]

> I support you having access to a porterbox, even if I'm not sure you shou=
> ld post it here...
>
> Don't we need to send a mail directly to DSA?
> please cc me and I'll endorse there too if needed,
> or even better if this mail is sufficient

According to documentation [1]


People who are not yet DMs or NMs will need to find a DD who is willing 
to sponsor their request. People
requesting access should already have a track record of working on 
Debian for sometime.

The guest applicant should supply several details(listedbelow) to this
DD, and the DD will sign this(clearsigned, not PGP mime) and open a
ticket in RT (mail to admin@rt.d.o,put'DebianRT'somewhere in the
subject-see wiki.d.o for more info).

This signing and resending is a sponsorship by the DD that the guest 
account should be granted
access to Debian resources, and should be regarded as such.

if you support my request, should sign information I attached, and open a 
ticket.

[1] https://dsa.debian.org/doc/guest-account/

-- 
Accept: text/plain, text/x-diff
Accept-Language: eo,en,ru
X-Web-Site: sinsekvu.github.io

Bug#823895: marked as done (RFS: lsm/1.0.4-1 [ITP])

[Debian Bug Tracking System]

Your message dated Wed, 27 Jul 2016 17:52:36 + (UTC)
with message-id <327104640.9877788.1469641956274.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#823895: RFS: lsm/1.0.4-1
has caused the Debian Bug report #823895,
regarding RFS: lsm/1.0.4-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.)


-- 
823895: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823895
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

Dear mentors,

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

* Package name: lsm
  Version : 1.0.4-1
  Upstream Author : Mika Ilmaranta 
* URL : http://lsm.foobar.fi/
* License : GPL-2
  Section : utils

  It builds those binary packages:

lsm   - Link connectivity monitor tool

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

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


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

dget -x https://mentors.debian.net/debian/pool/main/l/lsm/lsm_1.0.4-1.dsc




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Hi,

>If you can check what Adam Borowski had pointed, It'll be fine.


actually I checked it :)
>I uploaded a new version with spell patch.


and I uploaded it on new queue.

G.--- End Message ---

Re: Request for access to porterbox

[Gianfranco Costamagna]

On 27/07/2016 19:41, Dmitry Bogatov wrote:
> 
> Hello, I am looking for DD to sponsor my request for access a portbox
> to debug #832544, #832543.
> 
> Clear-signed information, required by DSA team is attached.
> 
> --
I support you having access to a porterbox, even if I'm not sure you should 
post it here...

Don't we need to send a mail directly to DSA?
please cc me and I'll endorse there too if needed,
or even better if this mail is sufficient

thanks!

G.




signature.asc
Description: OpenPGP digital signature

Request for access to porterbox

[Dmitry Bogatov]

Hello, I am looking for DD to sponsor my request for access a portbox
to debug #832544, #832543.

Clear-signed information, required by DSA team is attached.

--
Accept: text/plain, text/x-diff
Accept-Language: eo,en,ru
X-Web-Site: sinsekvu.github.io
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Name: Dmitry Bogatov
Preferred username: kaction
Key fingerprint: D1E0 591E 0037 BDCC BEE5  6002 788B E012 54B7 F00D
Agree to comply with DMUP (https://www.debian.org/devel/dmup): Yes
Architectures requested: hurd, m68k, sh4
Rationaly: reproduce #832544, #832543
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJXmPGtAAoJEHiL4BJUt/ANFroP/AvKlGkQ7ZXCc9ECS53v8qR8
eiLqdxqJoQ9+TIMFmdeF/D0EaxjVHARIkNVi8MiHTwqwg2qyGmXt5hviKGnY+X+O
NjsjUFf5z7mkgXbdBdOpBaKOGR7f38f1LzoJJ9RsKZIiHSYxdhbN6CfgmIXDUBA0
KKfXXxgKIDyLBSs2vssDBlFFAPR1fRyQHerXy0MUhDwCY4p2jaM4s0M+a/DTomBn
CHnHXBf6sS4aba11pk6FWtMFVvQO5CGndJ2NHMNOKKY2jpJPWMmG/yguRRvrH4WR
zOaPL0nGeK77GpKX9ls0aE6WkjlJU5mo360EZy8AlB8bVFvqsuZBtoqIKHW8Fn7O
jx45CldEH4O5HlWOYKe1AdlwF0gb3O4PiW5jzr8tLzQ6aEUqCqwWqg2B8BdB8WrU
/sCKfciV2WIzuyseEl93XUZ58lC/ve9brkr8FdDFT+hCEbfUhJMKqgweRv0QfLoq
qJ1qzP+sso4Ry3N1aFGQir4Jjl7rs+0giGU+EAbZ/NDmCDbHF5qrsWKFNsK5SQS7
6rvOgePG1C7gQEKf3GeVJP1MuK+ZtJHnLAwcet2XgiaSp3Gfzr/OqHM0XroxPTtm
GZ8CZXGZekWl9DQRs5093iTOdAHG9GSPN92bLGDz1rk9SqYdErOLD2uKAH2CBgri
aTy3UeBfynUidwRgblK0
=ov8a
-END PGP SIGNATURE-


pgpHc00b1jcD0.pgp
Description: PGP signature

Re: Bug#823895: RFS: lsm/1.0.4-1

[Lucas Castro]

On 27-07-2016 14:23, Gianfranco Costamagna wrote:
> Hi,
>
>
>> Who missing? I've checked, it's okay.
>
>
> you right
>
>> About that, it's a new version with some patches I've forwarded.
>> I'll wait for this version get in Debian to investigate the new version
>> changes.
>
> I can sponsor, or wait, let me know.
If you can check what Adam Borowski had pointed, It'll be fine.
> G.
I uploaded a new version with spell patch.



signature.asc
Description: OpenPGP digital signature

Re: [RFS] I need an sponsor for 2 Go packages

[Gianfranco Costamagna]

Hi,

>asciinema
>git.debian.org:/git/pkg-go/packages/asciinema.git
>https://mentors.debian.net/debian/pool/main/a/asciinema/asciinema_1.2.0-1.dsc


does the package looks like the old one to the end user?
if yes, please keep the previous changelog entries, the end user shouldn't care
too much about build changes, but more about functionalities changed.

>golang-github-creack-termios
>git.debian.org:/git/pkg-go/packages/golang-github-creack-termios.git
>https://mentors.debian.net/debian/pool/main/g/golang-github-creack-termios/golang-github-creack-termios_0.0~git20160520.0.01ff290-1.dsc
>
>I'm a DM, I already maintain other packages and have upload permissions,
>this uploads would close 3 bugs.


http://debomatic-amd64.debian.net/distribution#unstable/golang-github-creack-termios/0.0~git20160520.0.01ff290-1/lintian

fix lintian please and I'll try another review.

>I thank in advance any review/sponsor, upstream doesn't support the
>Python version anymore so I would like to have the Go version in time
>for the freeze


not an issue to me, we should have enough time.


G.

Bug#823895: RFS: lsm/1.0.4-1

[Gianfranco Costamagna]

Hi,


>Who missing? I've checked, it's okay.



you right

>About that, it's a new version with some patches I've forwarded.
>I'll wait for this version get in Debian to investigate the new version
>changes.


I can sponsor, or wait, let me know.

G.

Bug#832585: marked as done (RFS: gammaray/2.5.0-1 [RC] -- Tool for examining the internals of Qt application)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jul 2016 17:17:21 + (UTC)
with message-id <1060705258.9875534.1469639841795.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#832585: RFS: gammaray/2.5.0-1 [RC] -- Tool for 
examining the internals of Qt application
has caused the Debian Bug report #832585,
regarding RFS: gammaray/2.5.0-1 [RC] -- Tool for examining the internals of Qt 
application
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.)


-- 
832585: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832585
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for package "gammaray", whose source code is at:

  https://anonscm.debian.org/gitweb/?p=pkg-kde/kde-extras/gammaray.git

or you may also:

  dget -x 
https://mentors.debian.net/debian/pool/main/g/gammaray/gammaray_2.5.0-1.dsc

It builds these binary packages:

  gammaray - Tool for examining the internals of Qt application
  gammaray-probe-qt4 - GammaRay support for inspecting Qt4 applications
  gammaray-plugin-objectvisualizer - QObject hierarchy visualization plugin for 
GammaRay
  gammaray-plugin-quickinspector - GammaRay plugin for inspecting QtQuick2 
applications
  gammaray-plugin-kjobtracker - KJob tracker plugin for GammaRay
  gammaray-plugin-bluetooth - QtBluetooth type support for GammaRay
  gammaray-plugin-positioning - Qt5Positioning type support for GammaRay
  gammaray-dev - GammaRay plugin development files

Changes since the last upload:

gammaray (2.5.0-1) unstable; urgency=medium

  * New upstream release.
  * Migrate to automatic debug packages.
  * Use secure URIs in Vcs-* fields.
  * Bump Standards-Version to 3.9.8.
  * Refresh patches:
- debian-archs-fix-build.patch
- disable-qt4-objectvisualizer.patch
- disable-qt4-webinspector.patch.
  * Skip test failing on i386 prior Qt 4.7 (Closes: #826842).
  * Enable verbose output when running tests.

 -- Jakub Adam   Tue, 26 Jul 2016 09:35:26 +0200

Regards,

Jakub




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Hi,

>thanks for the review. I've fixed the issues in changelog and control file and 
>refreshed
>d/copyright with the missing licenses I was able to find. Most of the Lintian 
>warnings
>are also gone.



uploaded.
thanks!
G.--- End Message ---

Re: Bug#823895: RFS: lsm/1.0.4-1

[Lucas Castro]

On 27-07-2016 13:14, Gianfranco Costamagna wrote:
> Lets finish the review:
> 1)
>  
> grep copyright . -Ri
>
> missing people
Who missing? I've checked, it's okay.
> 2) 
> debian/upstream/changelog
>
> what^
> 3) did you forward patches upstream?
forwarded the changelog? His changelog is merged into spec file.
>
> if you can fix/answer the above I think we are good
>
> check-all-the-things review:
> $ codespell --quiet-level=3
> ./config.c:169: unkown  ==> unknown
> ./lsm.c:137: occured  ==> occurred
> ./lsm.spec:825: lisence  ==> license, licence
It is a false-positive, because the changelog is merged into this file,
so it's fix report in changelog.
> ./debian/lsm.init:12: conection  ==> connection
> ./debian/upstream/changelog:695: lisence  ==> license, licence
this file is extract from changelog, so is the same one above.
I'll fix the others.
>
> $ find -type d \( -iname .bzr -o -iname .git -o -iname .hg -o -iname .svn -o 
> -iname CVS -o -iname RCS -o -iname SCCS -o -iname _MTN -o -iname _darcs -o 
> -iname .pc -o -iname .cabal-sandbox -o -iname .cdv -o -iname .metadata -o 
> -iname CMakeFiles -o -iname _build -o -iname _sgbak -o -iname autom4te.cache 
> -o -iname blib -o -iname cover_db -o -iname node_modules -o -iname '~.dep' -o 
> -iname '~.dot' -o -iname '~.nib' -o -iname '~.plst' \) -prune -o -type f ! \( 
> -iname '*.bak' -o -iname '*.swp' -o -iname '#.*' -o -iname '#*#' -o -iname 
> 'core.*' -o -iname '*~' -o -iname '*.gif' -o -iname '*.jpg' -o -iname 
> '*.jpeg' -o -iname '*.png' -o -iname '*.min.js' -o -iname '*.js.map' -o 
> -iname '*.js.min' -o -iname '*.min.css' -o -iname '*.css.map' -o -iname 
> '*.css.min' \) -exec env PERL5OPT=-m-lib=. spellintian --picky {} +
>
>
> $ env PERL5OPT=-m-lib=. uscan --report-status --no-verbose
> uscan: Newest version of lsm on remote site is 1.0.5, local version is 1.0.4
> uscan:=> Newer package available from
> http://lsm.foobar.fi/download/lsm-1.0.5.tar.gz
About that, it's a new version with some patches I've forwarded.
I'll wait for this version get in Debian to investigate the new version
changes.
> G.

-- 
Lucas Castro



signature.asc
Description: OpenPGP digital signature

Bug#832585: RFS: gammaray/2.5.0-1 [RC] -- Tool for examining the internals of Qt application

[Jakub Adam]

Hi,

thanks for the review. I've fixed the issues in changelog and control file and 
refreshed
d/copyright with the missing licenses I was able to find. Most of the Lintian 
warnings
are also gone.

Updated in git & package re-uploaded to Mentors.

There's still a couple of minor issues reported by Lintian; you may upload the 
package as is,
or give me a day or two to sort them out as well.

Regards,

Jakub



signature.asc
Description: OpenPGP digital signature

Bug#832472: marked as done (RFS: django-memoize/2.0.0+dfsg-1 [ITP])

[Debian Bug Tracking System]

Your message dated Wed, 27 Jul 2016 16:19:38 + (UTC)
with message-id <1096812677.9739376.1469636378759.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#832472: RFS: django-memoize/2.0.0+dfsg-1 [ITP]
has caused the Debian Bug report #832472,
regarding RFS: django-memoize/2.0.0+dfsg-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.)


-- 
832472: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832472
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 "django-memoize"

 * Package name: django-memoize
   Version : 2.0.0+dfsg-1
   Upstream Author : Thadeus Burgess, Thomas Vavrys 
 * URL : https://pythonhosted.org/django-memoize/
 * License : BSD-3-clause
   Section : python

  It builds those binary packages:

 python-django-memoize - implementation of memoization technique for Django 
(Python 2)
 python-django-memoize-doc - implementation of memoization technique for Django 
(common documentation)
 python3-django-memoize - implementation of memoization technique for Django 
(Python 3)

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

  https://mentors.debian.net/package/django-memoize


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

dget -x 
https://mentors.debian.net/debian/pool/main/d/django-memoize/django-memoize_2.0.0+dfsg-1.dsc

  More information about django-memoize can be obtained from 
https://pythonhosted.org/django-memoize/.

  The VCS for the package is:

  https://anonscm.debian.org/cgit/python-modules/packages/django-memoize.git/

  Regards,
   Christopher Hoskin
--- End Message ---
--- Begin Message ---
Hi,

>  I am looking for a sponsor for my package "django-memoize"


LGTM, I put in deferred/4, to have some more time to check it :)

G.--- End Message ---

Bug#823895: RFS: lsm/1.0.4-1

[Gianfranco Costamagna]

Lets finish the review:
1)

grep copyright . -Ri

missing people

2) 
debian/upstream/changelog

what^
3) did you forward patches upstream?


if you can fix/answer the above I think we are good

check-all-the-things review:
$ codespell --quiet-level=3
./config.c:169: unkown  ==> unknown
./lsm.c:137: occured  ==> occurred
./lsm.spec:825: lisence  ==> license, licence
./debian/lsm.init:12: conection  ==> connection
./debian/upstream/changelog:695: lisence  ==> license, licence


$ find -type d \( -iname .bzr -o -iname .git -o -iname .hg -o -iname .svn -o 
-iname CVS -o -iname RCS -o -iname SCCS -o -iname _MTN -o -iname _darcs -o 
-iname .pc -o -iname .cabal-sandbox -o -iname .cdv -o -iname .metadata -o 
-iname CMakeFiles -o -iname _build -o -iname _sgbak -o -iname autom4te.cache -o 
-iname blib -o -iname cover_db -o -iname node_modules -o -iname '~.dep' -o 
-iname '~.dot' -o -iname '~.nib' -o -iname '~.plst' \) -prune -o -type f ! \( 
-iname '*.bak' -o -iname '*.swp' -o -iname '#.*' -o -iname '#*#' -o -iname 
'core.*' -o -iname '*~' -o -iname '*.gif' -o -iname '*.jpg' -o -iname '*.jpeg' 
-o -iname '*.png' -o -iname '*.min.js' -o -iname '*.js.map' -o -iname 
'*.js.min' -o -iname '*.min.css' -o -iname '*.css.map' -o -iname '*.css.min' \) 
-exec env PERL5OPT=-m-lib=. spellintian --picky {} +


$ env PERL5OPT=-m-lib=. uscan --report-status --no-verbose
uscan: Newest version of lsm on remote site is 1.0.5, local version is 1.0.4
uscan:=> Newer package available from
http://lsm.foobar.fi/download/lsm-1.0.5.tar.gz

G.

Bug#832400: marked as done (RFS: projectile/0.14.0-1 -- project interaction library for Emacs)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jul 2016 15:53:59 + (UTC)
with message-id <1822524648.7993634.1469634839552.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#832400: RFS: projectile/0.14.0-1 -- project 
interaction library for Emacs
has caused the Debian Bug report #832400,
regarding RFS: projectile/0.14.0-1 -- project interaction library for Emacs
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.)


-- 
832400: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for an update to projectile.  Although I have
DM upload rights for this package, this revision must pass through binNEW.

* Package name: projectile
  Version : 0.14.0-1
  Upstream Author : Bozhidar Batsov 
* URL : http://batsov.com/projectile/
* License : GPL-3+
  Section : lisp

Changes since the last upload:

  * New upstream release.
- elpa-persp-projectile & elpa-helm-projectile binary packages dropped.
  They now have their own source packages.
  * New projectile-doc binary package installing HTML manual.
- elpa-projectile Suggests: projectile-doc
- Add dh sequencer argument: --with linktree
- New build dependency on dh-linktree
- Add doc-base registration
- Add d/clean
- Add projectile-doc.lintian-overrides
  * Run test suite with dh_elpa_test.
- Bump debhelper compat to 10.
- Add source Lintian overrides:
  - package-needs-versioned-debhelper-build-depends
  - package-uses-experimental-debhelper-compat-version
  * Quilt patches:
- Append to 0001-patch-README.patch to remove screenshot.
  Screenshots now installed by projectile-doc.
- Drop 0003-fix-cleanup-known-projects-test.patch
  Merged upstream.
- Rename 0004-debianise-exuberant-ctags-dep.patch
  to 0003-debianise-exuberant-ctags-dep.patch
- Add 0004-drop-external-gratipay-image.patch
- Add 0005-configure-mkdocs-for-Debian.patch
- Refresh patches
  * d/copyright updates:
- bump copyright years and add upstream author's e-mail address
- remove paragraph for persp-projectile.el
  * Run wrap-and-sort -abst
  * Bump standards version to 3.9.8 (no changes required).

Download with dget:

dget -x 
http://mentors.debian.net/debian/pool/main/p/projectile/projectile_0.14.0-1.dsc

Or build it with gbp:

gbp clone --pristine-tar 
https://anonscm.debian.org/git/pkg-emacsen/pkg/projectile
git checkout debian/0.14.0-1
git verify-tag debian/0.14.0-1 # if you have my key
gbp buildpackage

Thanks.

Sean Whitton


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hi,

> gbp clone --pristine-tar 
> https://anonscm.debian.org/git/pkg-emacsen/pkg/projectile

> git checkout debian/0.14.0-1


moved to head and uploaded.


G.--- End Message ---

Bug#832246: marked as done (RFS: cligh/0.2-5 )

[Debian Bug Tracking System]

Your message dated Wed, 27 Jul 2016 15:46:42 + (UTC)
with message-id <1832849073.9823014.1469634402850.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#832246: RFS: cligh/0.2-5
has caused the Debian Bug report #832246,
regarding RFS: cligh/0.2-5 
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.)


-- 
832246: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832246
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 "cligh"

* Package name: cligh
  Version : 0.2-5
  Upstream Author : Christopher M. Brannon 
* Url : http://the-brannons.com/software/cligh.html
* Licenses: GPL-3+, BSD-3-clause
  Section : utils

It builds those binary packages:

cligh -- Command-line interface to GitHub

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

http://mentors.debian.net/package/cligh

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

dget -x http://mentors.debian.net/debian/pool/main/c/cligh/cligh_0.2-5.dsc

Alternatively, you can access package debian/ directory via git from URL:

https://anonscm.debian.org/cgit/users/kaction-guest/cligh.git

More information about cligh can be obtained from 
http://the-brannons.com/software/cligh.html

Changes since last upload:

  * Change section to 'utils'

Regards,
  Dmitry Bogatov
--- End Message ---
--- Begin Message ---
control: owner -1 !
control: tags -1 moreinfo


>I pinged upstream again, pointing to this hunk. If it will respond,
>upstream will release new version, and I will happily drop patches.


thanks, putting moreinfo in the meanwhile

G.--- End Message ---

Re: hardening Issue

[Gianfranco Costamagna]

Hi,


>sorry, thats because I put lintian-overrides.


mmm AFAIK DebOMatic looks also for overridden tags.

G.

Re: hardening Issue

[Andrey Rahmatullin]

On Wed, Jul 27, 2016 at 11:20:33AM -0300, Paulo wrote:
> I'm adopting package lostirc with problems to solve hardening issue.
> 
> The package builds ok but with lintian:
> I: lostirc: hardening-no-fortify-functions usr/bin/lostirc
> 
> blhc --all ../lostirc_0.4.6-5_amd64.build 
> Returns nothing but 
> 
> hardening-check -v debian/lostirc/usr/bin/lostirc 
> debian/lostirc/usr/bin/lostirc:
>  Position Independent Executable: yes
>  Stack protected: yes
>  Fortify Source functions: no, only unprotected functions found!
>   unprotected: memmove
>   unprotected: read
>   unprotected: memcpy
>   unprotected: gethostname
>   unprotected: recv
>  Read-only relocations: yes
>  Immediate binding: yes
> 
> I verified build log and I found flag: -D_FORTIFY_SOURCE=2 at all cpp compile 
> lines.
From the tag extended description:

NB: Due to false-positives, Lintian ignores some unprotected functions
(e.g. memcpy).

Refer to https://wiki.debian.org/Hardening and
https://bugs.debian.org/673112 for details.


-- 
WBR, wRAR


signature.asc
Description: PGP signature

Re: hardening Issue

[Paulo]

Hi Dmitry,

sorry, thats because I put lintian-overrides.

regards.

[]'s
kretcheu
:x


Em 27-07-2016 12:08, Dmitry Bogatov escreveu:
>> I'm adopting package lostirc with problems to solve hardening issue.
>>
>> The package builds ok but with lintian:
>> I: lostirc: hardening-no-fortify-functions usr/bin/lostirc
> 
> Can't reproduce it. The only warning I have is
> 
>   P: lostirc source: debian-watch-may-check-gpg-signature
> 
> Other opinions?
> 



signature.asc
Description: OpenPGP digital signature

Bug#832153: RFS: python-prov/1.4.0-1 [ITP]

[Gianfranco Costamagna]

His one is in new queue since an hour, so mine will be just rejected.


g.

Bug#832153: RFS: python-prov/1.4.0-1 [ITP]

[Ghislain Vaillant]

On 27/07/16 16:09, Gianfranco Costamagna wrote:

Hi,



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




as usual, built signed and sponsored.


G.


Thanks Gianfranco, although this time Yaroslav Halchenko from
NeuroDebian sponsored it first, but he did not link to the RFS. I
thought he would.

We might receive an alert that the upload was attempted twice. We'll
see.

Cheers,
Ghis

Re: hardening Issue

[Gianfranco Costamagna]

Hi,
>Can't reproduce it. The only warning I have is



I did a build a few hours ago on DoM
http://debomatic-amd64.debian.net/distribution#unstable/lostirc/0.4.6-5/buildlog

flags seems all in place.
but I might have missed some of them,

G.

Bug#832153: RFS: python-prov/1.4.0-1 [ITP]

[Gianfranco Costamagna]

Hi,


>I am looking for a sponsor for my package "python-prov"



as usual, built signed and sponsored.


G.

Bug#832142: marked as done (RFS: nbformat/4.0.1-1 (ITP in experimental!))

[Debian Bug Tracking System]

Your message dated Wed, 27 Jul 2016 15:07:32 + (UTC)
with message-id <1024670192.9672166.1469632052164.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#832142: RFS: nbformat/4.0.1-1 (ITP in experimental!)
has caused the Debian Bug report #832142,
regarding RFS: nbformat/4.0.1-1 (ITP in experimental!)
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.)


-- 
832142: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832142
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 "nbformat"

 * Package name: nbformat
   Version : 4.0.1-1
   Upstream Author : Jupyter Development Team
 * URL : https://github.com/jupyter/nbformat
 * License : BSD-3-clause
   Section : python

  It builds those binary packages:

python-nbformat - Jupyter notebook format (Python 2)
 python-nbformat-doc - Jupyter notebook format (documentation)
 python3-nbformat - Jupyter notebook format (Python 3)

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


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


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

dget -x 
https://mentors.debian.net/debian/pool/main/n/nbformat/nbformat_4.0.1-1.dsc


  It is packaged within the Debian Python Modules Team:
Vcs-Git: https://anonscm.debian.org/git/python-modules/packages/nbformat.git
Vcs-Browser: 
https://anonscm.debian.org/cgit/python-modules/packages/nbformat.git


 This packaging work is part of the effort to get Jupyter in Debian.

 Cheers,

Snark on #debian-python
--- End Message ---
--- Begin Message ---
Hi,



>   I am looking for a sponsor for my package "nbformat"


done, good luck for the other jupyter packages :)

G.--- End Message ---

Re: hardening Issue

[Dmitry Bogatov]

> I'm adopting package lostirc with problems to solve hardening issue.
>
> The package builds ok but with lintian:
> I: lostirc: hardening-no-fortify-functions usr/bin/lostirc

Can't reproduce it. The only warning I have is

P: lostirc source: debian-watch-may-check-gpg-signature

Other opinions?

-- 
Accept: text/plain, text/x-diff
Accept-Language: eo,en,ru
X-Web-Site: sinsekvu.github.io

Bug#830417: marked as done (RFS: django-setuptest/0.2.1-1 [ITP])

[Debian Bug Tracking System]

Your message dated Wed, 27 Jul 2016 14:54:25 + (UTC)
with message-id <151036176.9629338.1469631265972.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#830417: RFS: django-setuptest/0.2.1-1 [ITP]
has caused the Debian Bug report #830417,
regarding RFS: django-setuptest/0.2.1-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.)


-- 
830417: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830417
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist
X-Debbugs-CC: python-modules-t...@lists.alioth.debian.org

  Dear mentors,

  I am looking for a sponsor for my package "django-setuptest"

 * Package name: django-setuptest
   Version : 0.2.1-1
   Upstream Author : Praekelt Consulting 
 * URL : https://github.com/praekelt/django-setuptest/
 * License : BSD
   Section : python

  It builds those binary packages:

python-django-setuptest - simple test suite enabling Django app testing via 
setup.py (Python 2)
python3-django-setuptest - simple test suite enabling Django app testing 
via setup.py (Python 3)

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

  https://mentors.debian.net/package/django-setuptest


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

dget -x 
https://mentors.debian.net/debian/pool/main/d/django-setuptest/django-setuptest_0.2.1-1.dsc

  More information about django-setuptest can be obtained from 
https://github.com/praekelt/django-setuptest/.

  Regards,
   Christopher Hoskin
--- End Message ---
--- Begin Message ---

>I have now checked the package into the python-modules Alioth repository:


it looked good to me, uploaded.

G.--- End Message ---

hardening Issue

[Paulo]

Hi Mentors,

I'm adopting package lostirc with problems to solve hardening issue.

The package builds ok but with lintian:
I: lostirc: hardening-no-fortify-functions usr/bin/lostirc

blhc --all ../lostirc_0.4.6-5_amd64.build 
Returns nothing but 

hardening-check -v debian/lostirc/usr/bin/lostirc 
debian/lostirc/usr/bin/lostirc:
 Position Independent Executable: yes
 Stack protected: yes
 Fortify Source functions: no, only unprotected functions found!
unprotected: memmove
unprotected: read
unprotected: memcpy
unprotected: gethostname
unprotected: recv
 Read-only relocations: yes
 Immediate binding: yes

I verified build log and I found flag: -D_FORTIFY_SOURCE=2 at all cpp compile 
lines.
I uploaded to mentors.

https://mentors.debian.net/debian/pool/main/l/lostirc/lostirc_0.4.6-5.dsc

Can you help me?

Thanks
[]'s
kretcheu
:x



signature.asc
Description: OpenPGP digital signature

Bug#832585: RFS: gammaray/2.5.0-1 [RC] -- Tool for examining the internals of Qt application

[Tiago Ilieve]

Gianfranco,

On 27 July 2016 at 08:34, Gianfranco Costamagna
 wrote:
> Vcs-Git: https://anonscm.debian.org/pkg-kde/kde-extras/gammaray.git
> Vcs-Browser: 
> https://anonscm.debian.org/gitweb/?p=pkg-kde/kde-extras/gammaray.git
>
> they seem both wrong, please fix (the second one needs /cgit/, the first 
> /git/)

The first one gives a 404 error, but the "/git" URL[1] works for both
web and git clone access. This was fixed by Alexander Wirt earlier
this year, as "I now gives you either git smart http transport or the
cgit website of the project, depending on what you are asking for."[2]

I find this quite useful, as you don't have to worry about a single
'c' in the entire URL.

Regards,
Tiago.

[1]: https://anonscm.debian.org/git/pkg-kde/kde-extras/gammaray.git
[2]: https://lists.debian.org/debian-devel/2016/01/msg00333.html

-- 
Tiago "Myhro" Ilieve
Blog: https://blog.myhro.info/
GitHub: https://github.com/myhro
LinkedIn: https://br.linkedin.com/in/myhro
Montes Claros - MG, Brasil

Bug#832585: RFS: gammaray/2.5.0-1 [RC] -- Tool for examining the internals of Qt application

[Gianfranco Costamagna]

control: owner -1 !
control: tags -1 moreinfo


>ITYM 5.7.


Indeed, please fix.

since I reported the upstream issues, and did a lot of work on gammaray, I'll 
sponsor the
package.

Review:

1)

Vcs-Git: https://anonscm.debian.org/pkg-kde/kde-extras/gammaray.git
Vcs-Browser: 
https://anonscm.debian.org/gitweb/?p=pkg-kde/kde-extras/gammaray.git

they seem both wrong, please fix (the second one needs /cgit/, the first /git/)

2) I don't like disabling tests, but you are right on this, since the bug is in 
qt :(

3) missing copyrights:
+  Copyright (C) 2015-2016 Klarälvdalens Datakonsult AB, a KDAB Group company, 
i...@kdab.com
+  Author: Volker Krause 
+


bad copyright years (many needs bump)

gammaray-2.5.0/cmake/ECMQueryQmake.cmake
gammaray-2.5.0/cmake/QtInstallPaths.cmakegammaray-2.5.0/cmake/lots*.cmake
^^ missing licenses


+Licensees holding valid commercial KDAB GammaRay licenses may use this 
file in
+accordance with GammaRay Commercial License Agreement provided with the 
Software.
+
+Contact i...@kdab.com if any conditions of this licensing are not clear to 
you.
+
+This work is also licensed under the Creative Commons 
Attribution-ShareAlike 4.0
+International License. See 
.
+*/

^^ lots of missing


4) 
http://debomatic-amd64.debian.net/distribution#unstable/gammaray/2.5.0-1/lintian


lots of them can be easily fixed


other stuff LGTM,
I tested both amd64 and i386 with success.

thanks,

G.

Bug#832585: RFS: gammaray/2.5.0-1 [RC] -- Tool for examining the internals of Qt application

[Andrey Rahmatullin]

On Wed, Jul 27, 2016 at 11:05:08AM +0200, Jakub Adam wrote:
>   * Skip test failing on i386 prior Qt 4.7 (Closes: #826842).
ITYM 5.7.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#832585: RFS: gammaray/2.5.0-1 [RC] -- Tool for examining the internals of Qt application

[Jakub Adam]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for package "gammaray", whose source code is at:

  https://anonscm.debian.org/gitweb/?p=pkg-kde/kde-extras/gammaray.git

or you may also:

  dget -x 
https://mentors.debian.net/debian/pool/main/g/gammaray/gammaray_2.5.0-1.dsc

It builds these binary packages:

  gammaray - Tool for examining the internals of Qt application
  gammaray-probe-qt4 - GammaRay support for inspecting Qt4 applications
  gammaray-plugin-objectvisualizer - QObject hierarchy visualization plugin for 
GammaRay
  gammaray-plugin-quickinspector - GammaRay plugin for inspecting QtQuick2 
applications
  gammaray-plugin-kjobtracker - KJob tracker plugin for GammaRay
  gammaray-plugin-bluetooth - QtBluetooth type support for GammaRay
  gammaray-plugin-positioning - Qt5Positioning type support for GammaRay
  gammaray-dev - GammaRay plugin development files

Changes since the last upload:

gammaray (2.5.0-1) unstable; urgency=medium

  * New upstream release.
  * Migrate to automatic debug packages.
  * Use secure URIs in Vcs-* fields.
  * Bump Standards-Version to 3.9.8.
  * Refresh patches:
- debian-archs-fix-build.patch
- disable-qt4-objectvisualizer.patch
- disable-qt4-webinspector.patch.
  * Skip test failing on i386 prior Qt 4.7 (Closes: #826842).
  * Enable verbose output when running tests.

 -- Jakub Adam   Tue, 26 Jul 2016 09:35:26 +0200

Regards,

Jakub




signature.asc
Description: OpenPGP digital signature

[RFS] I need an sponsor for 2 Go packages

[gustavo panizzo (gfa)]

Hello

I'm the maintainer of asciinema, a while ago upstream decided to rewrite
it in Go, previously it was a Python app.

I've made a package for it, and the 2 dependencies that were missing in
the archive, one of those dependencies was already sponsored/uploaded,
but the sponsor has no time to sponsor the 2 missing packages.

asciinema
git.debian.org:/git/pkg-go/packages/asciinema.git
https://mentors.debian.net/debian/pool/main/a/asciinema/asciinema_1.2.0-1.dsc

golang-github-creack-termios
git.debian.org:/git/pkg-go/packages/golang-github-creack-termios.git
https://mentors.debian.net/debian/pool/main/g/golang-github-creack-termios/golang-github-creack-termios_0.0~git20160520.0.01ff290-1.dsc

I'm a DM, I already maintain other packages and have upload permissions,
this uploads would close 3 bugs.

I thank in advance any review/sponsor, upstream doesn't support the
Python version anymore so I would like to have the Go version in time
for the freeze



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

keybase: http://keybase.io/gfa


signature.asc
Description: PGP signature