Re: Debian packaging with meson
On Sat, Feb 18, 2017 at 04:34:34AM +0100, Adam Borowski wrote: > 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 provides /usr/sbin/ninja, but ninja-build > > Conflicts: ninja. > > Tsk, naughty. > > You know this violated a "must" clause of the Policy, that's there for a > good reason? Why do you assume that _I_ did this? I'm just stating what the packaging is doing. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#855452: ITP: el-x -- Emacs Lisp extensions
Package: wnpp Severity: wishlist Owner: Lev Lamberov * Package name: el-x Version : 0.3.1 Upstream Author : Yann Hodique * URL : https://github.com/sigma/el-x * License : GPL-2+ Programming Lang: Emacs Lisp Description : Emacs Lisp extensions This package provides several Emacs Lisp extensions. Content: * dflet.el: defines the `dflet' macro, to provide the historic behavior of `flet', a global and dynamic temporary function (re)definition tool. * subr-compat.el: stubs `declare-function' for older Emacs
Bug#855454: ITP: mocker-el -- mocking framework for Emacs
Package: wnpp Severity: wishlist Owner: Lev Lamberov * Package name: mocker-el Version : 0.3.1 Upstream Author : Yann Hodique * URL : https://github.com/sigma/mocker.el * License : GPL-2+ Programming Lang: Emacs Lisp Description : mocking framework for Emacs This package is helpful with testing Emacs Lisp code. Its single entry point (`mocker-let') provides an `let' like interface to defining mock objects. Actually, `mocker-let' is a wrapper around `flet', which can be seen as a way to manually generate mocks.
Re: [openstack-dev] The end of OpenStack packages in Debian?
On 2/15/17 8:22 PM, gustavo panizzo wrote: On Wed, Feb 15, 2017 at 01:42:51PM +0100, Thomas Goirand wrote: Hi there, Its really sad news, for both You and OpenStack & Debian. Thank you for your work, Thomas -- I hope you are able to continue it. I'm slow on the uptake here, for which I apologize. Does this announcement mean that the Mirantis apt servers (e.g. mitaka-jessie.pkgs.mirantis.com) will also be discontinued, or are we only talking about package contributions to the official Debian distros? Relatedly... is Mirantis likely to make some sort of announcement or commitment about the lifespan of that service? Or is it just there until it's not? -Andrew
Re: changelog practice, unfinalised vs UNRELEASED vs ~version
Hi Ian, On Sun, Feb 12, 2017 at 12:48:35PM +, Ian Jackson wrote: > We do not seem to have a coherent approach to how to handle > debian/changelog in trees (eg, vcs branches) which are not yet ready > for upload. > > See below two examples of things done differently. > The questions are: > > Q1. Should the suite in the changelog entry be UNRELEASED, > or the suite at which the vcs branch is targeted ? DEP14 allows for branching schemes that have the desired suite included like debian/sid, debian/experimental, debian/stretch so the information is included in the VCS and UNRELEASED only indicates the "not finished yet" part. > Q2. Should the changelog entry be finalised ? That is, should it > have an uploader name and date ? > > Q3. Should the version number be the intended next version number, > or should it be decorated with ~something ? If it should > be decorated, what should it be decorated with ? gbp dch adds a ~.gbp by default. N being the snapshot number (the nth time you ran dbp dch since the last release) and being the first digits of the sha1. This allows for * easy identification of snapshot builds * increasing version numbers useful for e.g. CI builds. * a version number that is smaller than the final release number so systems having snapshot builds can be easily upgraded to release versions * a mapping back to the git commit until when the changelog was filled. Cheers, -- Guido
Re: Is lack of full-HD display support an RC bug?
On Mon, 6 Feb 2017 23:01:39 +0100, Dominik George wrote: >xrdp, a remote desktop server for X.org, has an (upstream) bug that >makes it impossible to use it from clients with high resolutions, like >1920x1080. Is this already filed in Debian? If so, what's the bug number, and what are the symptoms of this bug? Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber | " Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/ Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834
Re: Is lack of full-HD display support an RC bug?
Marc Haber: > On Mon, 6 Feb 2017 23:01:39 +0100, Dominik George > wrote: >> xrdp, a remote desktop server for X.org, has an (upstream) bug that >> makes it impossible to use it from clients with high resolutions, like >> 1920x1080. > > Is this already filed in Debian? If so, what's the bug number, and > what are the symptoms of this bug? > > Greetings > Marc > Possibly related: """ [...] Date: Sat, 18 Feb 2017 16:46:17 +0100 [...] Changes: xrdp (0.9.1-7) unstable; urgency=medium . * Fix RFX with large tile sets, e.g. full HD displays. (Closes: #855387) [...] """ https://tracker.debian.org/news/839034 Thanks, ~Niels
Re: [openstack-dev] The end of OpenStack packages in Debian?
On 02/18/2017 05:14 PM, Andrew Bogott wrote: > Does this > announcement mean that the Mirantis apt servers (e.g. > mitaka-jessie.pkgs.mirantis.com) will also be discontinued Correct, I've been told the server would be decommitionned. In fact, I'm surprised it is still up-and-running. I've explained that some people could well still be using it, but it didn't seem someone cared. FYI, I made a backup on my own laptop, but I don't plan on investing a dime on setting-up an online service myself. > Relatedly... is Mirantis likely to make some sort of announcement or > commitment about the lifespan of that service? Or is it just there > until it's not? Since the end of 2016, I'm not a Mirantis employee, so I can't talk for them. I can only guess that it is very unlikely any announcement would be made. I'd very much welcome someone external from the company to express discontent to the Mirantis marketing team about discontinuation of this service. So be my guest... Cheers, Thomas Goirand (zigo)
Re: Is lack of full-HD display support an RC bug?
On 02/06/2017 11:50 PM, Holger Levsen wrote: > On Mon, Feb 06, 2017 at 11:27:53PM +0100, Dominik George wrote: >> But I figure I could handle this as important, so xrdp will not get >> removed if the patch doesn't migrate, and still ask for an unblock, >> which seems to be also possible for bugs with important severity. > > yup, this approach seems more reasonable. Looking at the description of the issue, it would also seem reasonable to attempt to fix it in Jessie. Cheers, Thomas Goirand (zigo)
Re: Personal Git repositories on Alioth
Ben Finney writes: > Wouter Verhelst writes: > > > […] for future reference, this is ridiculously easy for anyone who's > > a Debian Developer or otherwise has an account on alioth […] > Thank you. I completely overlooked the section about personal Git repositories on the https://wiki.debian.org/Alioth/Git> page. I have now made it a little easier to find on that page. -- \ “Begin with false premises and you risk reaching false | `\ conclusions. Begin with falsified premises and you forfeit your | _o__) authority.” —Kathryn Schulz, 2015-10-19 | Ben Finney
Re: [PKG-Openstack-devel] [openstack-dev] The end of OpenStack packages in Debian?
On Sun, Feb 19, 2017 at 01:10:21AM +0100, Thomas Goirand wrote: On 02/18/2017 05:14 PM, Andrew Bogott wrote: Does this announcement mean that the Mirantis apt servers (e.g. mitaka-jessie.pkgs.mirantis.com) will also be discontinued Correct, I've been told the server would be decommitionned. In fact, I'm surprised it is still up-and-running. I've explained that some people could well still be using it, but it didn't seem someone cared. FYI, I made a backup on my own laptop, but I don't plan on investing a dime on setting-up an online service myself. how much space does it need? do you have all openstack releases? i'll try to get a place for them, no promises are made thanks Zigo -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: https://keybase.io/gfa signature.asc Description: PGP signature
Re: De-Branding of Icedove, reintroducing Thunderbird packages into Debian
Mike Hommey wrote: > Why not just create a ~/.thunderbird symlink to ~/.icedove if > ~/.icedove exists? This seems like the right solution. (Or, equivalently, rename ~/.icedove to ~/.thunderbird and place a symlink in the other direction.) Any particular reason not to do this? - Josh Triplett
Re: [openstack-dev] The end of OpenStack packages in Debian?
]] Thomas Goirand > On 02/18/2017 05:14 PM, Andrew Bogott wrote: > > Does this > > announcement mean that the Mirantis apt servers (e.g. > > mitaka-jessie.pkgs.mirantis.com) will also be discontinued > > Correct, I've been told the server would be decommitionned. In fact, I'm > surprised it is still up-and-running. I've explained that some people > could well still be using it, but it didn't seem someone cared. > > FYI, I made a backup on my own laptop, but I don't plan on investing a > dime on setting-up an online service myself. You could talk to Packagecloud and see if they're interested. Not sure what the size of the repo is, their open source offering is for up to 25G. -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are
Re: De-Branding of Icedove, reintroducing Thunderbird packages into Debian
Hello, Am 19.02.2017 um 07:12 schrieb Josh Triplett: > Mike Hommey wrote: >> Why not just create a ~/.thunderbird symlink to ~/.icedove if >> ~/.icedove exists? > > This seems like the right solution. (Or, equivalently, rename > ~/.icedove to ~/.thunderbird and place a symlink in the other > direction.) > > Any particular reason not to do this? given to the feedback on the list and BTS we will change the current behavior to "just" symlink to ~/.icedove. While starting the process of the package migration we (mostly me) was worry about we have to do much more changes inside a users profile and it would be good to have a full backup. But now it turns out it isn't that much. I'd like to thank all the people who gave us suggestions and helpful feedback in the past days and weeks! We can make Thunderbird great again in Debian. :-) -- Regards Carsten Schoenert
