Excerpts from Barry Warsaw's message of 2017-02-16 16:58:08 -0500:
> Hi Thomas,
>
> I'm very sorry to hear this, and of course I hope that everything eventually
> works out for you. I really appreciate the work you've done on
> openstack-devel packages that are useful to the wider Python communit
On Sat, Feb 18, 2017 at 9:39 AM, Ben Finney wrote:
> Does the resulting repository automatically get published on Alioth,
> managed by ‘cgit’ at a ‘anonscm.debian.org’ URL?
cgit doesn't do any management, it just publishes existing repos.
User repositories are available at URLs like these:
http
On Fri, Feb 17, 2017 at 10:07:12PM -0500, James McCoy wrote:
> On Sat, Feb 18, 2017 at 03:28:58AM +0100, Adam Borowski wrote:
> > Note that this won't work unless we rename ninja-build to ninja.
>
> Why not? ninja-build has been providing /usr/bin/ninja since it was
> first uploaded. Yes, ninja
On Sat, Feb 18, 2017 at 03:28:58AM +0100, Adam Borowski wrote:
> On Fri, Feb 17, 2017 at 11:29:35PM +, Simon McVittie wrote:
> > On Fri, 17 Feb 2017 at 18:08:01 -0500, Jeremy Bicha wrote:
> > > GNOME 3.24 modules have begun including meson build scripts.
> >
> > It looks as though Meson approx
On Fri, Feb 17, 2017 at 11:29:35PM +, Simon McVittie wrote:
> On Fri, 17 Feb 2017 at 18:08:01 -0500, Jeremy Bicha wrote:
> > GNOME 3.24 modules have begun including meson build scripts.
>
> It looks as though Meson approximately follows the Autotools-like
> build pipeline that dh assumes, so s
Wouter Verhelst writes:
> […] for future reference, this is ridiculously easy for anyone who's a
> Debian Developer or otherwise has an account on alioth:
>
> ssh to git.debian.org, and run:
>
> mkdir -p public_git/repo.git
> cd public_git/repo.git
> git init --bare
>
> log out again; then, in yo
Simon McVittie:
> On Fri, 17 Feb 2017 at 18:08:01 -0500, Jeremy Bicha wrote:
>> GNOME 3.24 modules have begun including meson build scripts.
>
> It looks as though Meson approximately follows the Autotools-like
> build pipeline that dh assumes, so something like this should work:
>
> override_dh_
2017-02-18 0:29 GMT+01:00 Simon McVittie :
> On Fri, 17 Feb 2017 at 18:08:01 -0500, Jeremy Bicha wrote:
>> GNOME 3.24 modules have begun including meson build scripts.
>
> It looks as though Meson approximately follows the Autotools-like
> build pipeline that dh assumes, so something like this shou
On Fri, 17 Feb 2017 at 18:08:01 -0500, Jeremy Bicha wrote:
> GNOME 3.24 modules have begun including meson build scripts.
It looks as though Meson approximately follows the Autotools-like
build pipeline that dh assumes, so something like this should work:
override_dh_auto_clean:
rm -fr de
GNOME 3.24 modules have begun including meson build scripts.
Currently, autotools is still supported, but at least one developer
[1] has said that meson will be the only way to build his app for
GNOME 3.26. (GNOME 3.26 is scheduled for release in September.)
Has anyone trying making Debian packag
Santiago Vila:
> On Fri, Feb 17, 2017 at 06:23:00AM +, Niels Thykier wrote:
>
>> Santiago already brought it up in #844264. I believe my answer in
>> comment 70 is still relevant (other than I incorrectly used "after the
>> freeze" when I meant "after the release").
>
> Well, but when I said
On Fri, Feb 17, 2017 at 08:54:54AM -0600, Jeff Epler wrote:
> On Fri, Feb 17, 2017 at 12:16:16PM +0100, Santiago Vila wrote:
> > Can anyone here reproduce any of the following *two* bugs?
> > (Using sbuild in a single-CPU machine)
> >
> > 837067 1.000 libsecret
>
> Using a fresh 1CPU / 1GB x86
On Fri, Feb 17, 2017 at 03:34:08PM +, Holger Levsen wrote:
> https://tests.reproducible-builds.org/libsecret looks better:
I forgot to mention this (kind of) URL:
https://tests.reproducible-builds.org/debian/history/libsecret.html
--
cheers,
Holger
signature.asc
Description: Di
On Fri, Feb 17, 2017 at 08:54:54AM -0600, Jeff Epler wrote:
> On Fri, Feb 17, 2017 at 12:16:16PM +0100, Santiago Vila wrote:
> > Can anyone here reproduce any of the following *two* bugs?
> > (Using sbuild in a single-CPU machine)
> > 837067 1.000 libsecret
>
> Using a fresh 1CPU / 1GB x86 syst
On Fri, Feb 17, 2017 at 12:16:16PM +0100, Santiago Vila wrote:
> Can anyone here reproduce any of the following *two* bugs?
> (Using sbuild in a single-CPU machine)
>
> 837067 1.000 libsecret
Using a fresh 1CPU / 1GB x86 system on digitalocean's NYC region, upgraded to
debian testing, I tried
Package: wnpp
Severity: wishlist
Owner: Andreas Tille
* Package name: examl
Version : 3.0.18
Upstream Author : Alexandros Stamatakis
* URL : https://github.com/stamatak/ExaML
* License : GPL
Programming Lang: C
Description : Exascale Maximum Likelihood
Package: wnpp
Severity: wishlist
Owner: Lev Lamberov
* Package name: elisp-bug-hunter
Version : 1.3.1
Upstream Author : Artur Malabarba
* URL : https://elpa.gnu.org/packages/bug-hunter.html
GitHub URL : https://github.com/Malabarba/elisp-bug-hunter
* License
Package: wnpp
Owner: Free Ekanayaka
Severity: wishlist
* Package name: automat
Version : 0.5.0
Upstream Author : Glyph Lefkowitz
* URL or Web page : https://github.com/glyph/Automat
* License : Expat
Description : Self-service finite-state machines for the programme
On Fri, Feb 17, 2017 at 06:23:00AM +, Niels Thykier wrote:
> Santiago already brought it up in #844264. I believe my answer in
> comment 70 is still relevant (other than I incorrectly used "after the
> freeze" when I meant "after the release").
Well, but when I said "Ok, will do" in Bug #844
Le 16/02/2017 à 20:00, Carsten Schoenert a écrit :
> Am 16.02.2017 um 19:26 schrieb Michael Biebl:
>> You already have a NEWS entry for the de-branding which talks about the
>> user profile. Maybe add an additional section there, that the old
>> profile is kept as ~/.icedove and that the user can d
20 matches
Mail list logo
