Re: User-installable Debian packages?

2017-07-25 Thread Florian Weimer
* Simon McVittie:

> On Sat, 22 Jul 2017 at 12:28:04 +0200, Steffen Möller wrote:
>> And quite some packages in our
>> distribution do not really need to be installed as root if they were
>> installed where the user has write permissions. There would hence be
>> little overhead over what we have now. Should we not somehow find ways
>> to tag any such location-agnostic packages and prepare dpkg for
>> installing e.g. in $HOME/.debian when it is executed as non-root?
>
> Rather than inventing a new wheel and having another Debian-specific
> thing that can only be used on Debian (and not even on derivatives
> without it being a "Frankendebian" system), might it be better to use
> Debian's source, binaries or a mixture of the two as input to creating
> something cross-distribution like Flatpak, AppImage or Snap? I would
> personally recommend Flatpak.

But it's not clear if the HPC community wants to run
containers/namespaces at all.  Maybe Steffen can comment.



Bug#869650: ITP: golang-github-hashicorp-go-rootcerts -- Functions for loading root certificates for TLS connections.

2017-07-25 Thread Shengjing Zhu
Package: wnpp
Severity: wishlist
Owner: Shengjing Zhu 

* Package name: golang-github-hashicorp-go-rootcerts
  Version : 0.0~git20160503.0.6bb64b3-1
  Upstream Author : HashiCorp
* URL : https://github.com/hashicorp/go-rootcerts
* License : MPL-2.0
  Programming Lang: Go
  Description : Functions for loading root certificates for TLS connections.

 Go's standard library crypto/tls provides a common mechanism for
 configuring TLS connections in tls.Config. The RootCAs field on this
 struct is a pool of certificates for the client to use as a trust store
 when verifying server certificates.
 .
 This library contains utility functions for loading certificates destined
 for that field, as well as one other important thing:
 .
 When the RootCAs field is nil, the standard library attempts to
 load the host's root CA set.  This behavior is OS-specific, and
 the Darwin implementation contains a bug that prevents trusted
 certificates from the System and Login keychains from being loaded
 This library contains Darwin-specific behavior that works around
 that bug.

 I'm intend to package this inside pkg-go team, and I need sponsor to upload.

 This library is a new dependency of golang-github-hashicorp-atlas-go-dev, which
 is needed for new packer(https://bugs.debian.org/865337).


signature.asc
Description: PGP signature


Bug#869654: ITP: no-resource-uri-leak -- browser extension for improving privacy by denying resource:// access to Web content.

2017-07-25 Thread Hema Prathaban
Package: wnpp
Severity: wishlist
Owner: Hema Prathaban 

* Package name: no-resource-uri-leak
  Version : 0.2.1
  Upstream Author : nord-stream 
* URL : https://notabug.org/desktopd/no-resource-uri-leak/
* License : GPL-3+, MPL-2.0
  Programming Lang: Javascript
  Description : browser extension for improving privacy by denying
resource:// access to Web content.

This extension hides private and important meta-data of your browser, usually
obtainable using resource:// URIs, against the Web.Improves privacy to Firefox.



Re: building a debian kernel package(s) for a foreign architecture

2017-07-25 Thread Roger Shimizu
Dear Jonathan,

How is your build? Does it go well?

On Thu, Jul 6, 2017 at 2:38 AM, Ben Hutchings  wrote:
> On Wed, 2017-07-05 at 23:43 +0900, Roger Shimizu wrote:
>>
>> I ever created one:
>> - https://wiki.debian.org/HowToCrossBuildAnOfficialDebianKernelPackage
>>
>> Hope it helps you.
>> And if you find something not current and need modify, please just edit it.
>> Thank you!
>
> Why does that talk about building from the git repository, rather than
> a source package (which duplicates the instructions at
> https://kernel-handbook.alioth.debian.org/ch-common-tasks.html)?
>
> For cross-building generally you should use the 'cross' build profile.
> And for linux specifically you can also use the 'pkg.linux.notools'
> build profile to disable the userland packages, which greatly reduces,
> the build depdendencies.

Dear Ben,

I created the wiki entry because I want to explorer some other ways
than what's telling in the kernel handbook. Of course I take the
handbook as reference, and thanks for your work!

It's easy to reproduce a kernel build by the steps in kernel handbook,
but what I want, sometimes, is to try the latest stable kernel
released upstream. Debian usually lags a few days behind upstream's
new release, especially in the freeze stage before a debian release.
So I think my wiki entry is informative in such case.

And I happened to find another topic in kernel lists:
 - 
http://debian.2.n7.nabble.com/cross-building-linux-image-packages-td3974626.html

I tried your suggested command:
  dpkg-buildpackage -Pcross,nopython -aarmel -B -uc -us
but got the following error:


dpkg-source: error: cannot read debian-kernel/debian/control: No such
file or directory
dpkg-buildpackage: error: dpkg-source --before-build debian-kernel
gave error exit status 2



On Thu, Jul 6, 2017 at 2:53 AM, Karsten Merker  wrote:
> On Wed, Jul 05, 2017 at 03:35:25PM +0100, Jonathan Dowland wrote:
>> Hi folks,
>>
>> I've never done much in the way of cross-compiling before.  I
>> understand it was once very hard, is now much easier, and is
>> considerably easier for "simple" packages (including the kernel)
>> than others.
>>
>> That said, I'm lost/stuck trying to cross-compile the Debian
>> Linux kernel package for ARM64 (target is a Raspberry Pi 3) from
>> an amd64 builder.  I believe I do not need to use multiarch for
>> my builder, yet dpkg-buildpackage (if I supply -a aarch64,
>> interestingly ARM64 doesn't work) complains of unmet build
>> dependencies, which I have resolved for amd64.  But perhaps -a to
>> dpkg-buildpackage is the wrong approach.
>
> Hello,
>
> from a technical point of view you effectively need multiarch to
> crosscompile Debian packages, but you don't have to set it up
> yourself ;-).
>
> The easiest way to crossbuild a Debian package is probably to use
> sbuild or pbuilder, which both have crossbuild-support since a
> while.  When called with the appropriate options, they
> automatically setup multiarch in their chroot and install the
> necessary crosscompilers as well as the package cross-dependencies.
> I can only talk about sbuild from personal experience, but
> according to the docs, pbuilder should work similarly.
>
> Not all packages can be crossbuilt, and for those that can be
> crossbuilt in principle, it is sometimes necessary to set
> appropriate build-profiles which e.g. cause the testsuite not to
> be run during the package build, as often the testsuite tries to
> run host-architecture binaries created during the build which
> cannot be executed on the build-architecture system (with "build"
> and "host" used in GNU terminology, i.e. "build-architecture" =
> "architecture on which the compiler runs" and "host-architecture" =
> "architeture on which the created binaries run").
>
> IIRC both pbuilder and sbuild automatically set the "nocheck"
> profile when crossbuilding. For crossbuilding the kernel IIRC
> one needs to set a number of additional build-profiles:
>
> - cross
> - pkg.linux.notools
> - nopython
>
> So the following sbuild command should in theory (sorry, cannot
> actually test that right now) crossbuild the kernel package for
> arm64:
>
>   sbuild -d unstable --host=arm64 --profiles=cross,pkg.linux.notools,nopython 
> .dsc

Thanks for your sample on sbuild, and detailed profile options.
I usually use git-pbuild for other packages. I hasn't figure out how
to do cross build kernel under pbuilder or its related tool (e.g.
git-build)
So if anybody know it, please let me know. Thanks!

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1



Bug#869690: ITP: jpm.sh -- tool for Firefox add-on development without Node.js dependencies

2017-07-25 Thread Hema Prathaban
Package: wnpp
Severity: wishlist
Owner: Hema Prathaban 

* Package name: jpm.sh
  Version : 1.0
  Upstream Author : nord-stream , 
Erik Vold 
* URL : https://notabug.org/desktopd/jpm.sh
* License : GPL-3+, MPL-2.0, AGPL-3.0
  Programming Lang: Shellscript, Javascript
  Description : tool for Firefox add-on development without Node.js 
dependencies

jpm.sh offers Firefox add-on development without Node.js dependencies 
by having pure /bin/sh solution.

This tool is build dependency for no-resource-uri-leak (ITP:#869654)



Bug#869730: ITP: featherpad -- FeatherPad is a lightweight Qt5 plain-text editor for Linux

2017-07-25 Thread Alf Gaida
Package: wnpp
Severity: wishlist
Owner: Alf Gaida 

* Package name: featherpad
  Version : 0.6
  Upstream Author : Tsu Jan 
* URL : https://github.com/tsujan/FeatherPad
* License : GPL
  Programming Lang: C++
  Description : FeatherPad is a lightweight Qt5 plain-text editor for Linux

FeatherPad (by Pedram Pourang, a.k.a. Tsu Jan ) is a 
lightweight Qt5 plain-text 
editor for Linux. It is independent of any desktop environment and has:

* Drag-and-drop support, including tab detachment and attachment;
* X11 virtual desktop awareness (using tabs on current desktop but opening a 
new window on another);
* An optionally permanent search-bar with a different search entry for each tab;
* Instant highlighting of found matches when searching;
* A docked window for text replacement;
* Support for showing line numbers and jumping to a specific line;
* Automatic detection of text encoding as far as possible and optional saving 
with encoding;
* Syntax highlighting for common programming languages;
* Printing;
* Text zooming;
* Appropriate but non-interrupting prompts;

 - Lightweight Qt Editor, replacement for the more or less dead Juffed in LXQt
 - pkg-lxqt will maintain it 



Bug#869749: RFP: dsmidiwifi -- DS Midi Wifi server

2017-07-25 Thread Fernando Toledo
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org

--- Please fill out the fields below. ---

   Package name: dsmidiwifi
Version: 0~git20130801+6ad682e-1
Upstream Author: _0xtob 
URL: http://dsmi.tobw.net/
License: GPL2
Description: Nintendo DS MIDI WiFi Server

 This application is used to forward MIDI messages between  local MIDI
 applications and Nintendo DS handhelds in the local network.
 .
 For more information, visit http://dsmi.tobw.net
 .
 Also, many Android / iPhone apps use this protocol to connect
 remote midi mixers o controllers. This "procotol" is also known as "dsmi"
 .
You can us apps like Dj Control (author Borce Trajkovsky) and mixxx

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