Hi Paul,
On 06.03.2013 01:13, Paul Wise wrote:
> On Tue, Mar 5, 2013 at 2:57 PM, Arno Töll wrote:
>
>> dcut dm --uid "Tobias Stefan Richter" --allow nexus
>
> Could this be moved to devscripts as a dm command? Maybe with less
> dashes in the interface too.
the command is part of our dcut ("Debi
On Tue, Mar 5, 2013 at 2:57 PM, Arno Töll wrote:
> dcut dm --uid "Tobias Stefan Richter" --allow nexus
Could this be moved to devscripts as a dm command? Maybe with less
dashes in the interface too.
dm "Tobias Stefan Richter" allow foo bar , deny baz
--
bye,
pabs
http://wiki.debian.org/PaulWi
>> Note, you can also use dput-ng (available in unstable) to manage DM
>> permissions. The equivalent command would be:
>>
>> dcut dm --uid "Tobias Stefan Richter" --allow nexus
>>
>>
I have had good luck with yodack to set DM permission as well:
https://github.com/algernon/yodack
Cheers,
ton
Hi Joss,
On Tue, Mar 05, 2013 at 08:39:45PM +0100, Josselin Mouette wrote:
> while investigating on #699749 (which apparently affects many machines
> using NM, but not all of them), I discovered that the interface for
> ifupdown hooks has changed since squeeze.
> >From the manpage:
>Whe
On Wed, Mar 6, 2013 at 6:20 AM, Steve Langasek wrote:
> On Tue, Mar 05, 2013 at 08:28:15PM +0800, Paul Wise wrote:
>> Is there anything we can add to debcheck or the PTS to encourage
>> maintainers to help break these cycles by adding build profiles and or
>> cross-compilation info?
>
> It seems to
Hi Arno:
On Tue, 5 Mar 2013, Arno Töll wrote:
You missed the header. While the "Uploader" field is optional (and also
used for the mail confirmation you're missing by the way), the "Archive"
field is not. Moreover, the blank newline dividing the header from the
data part is required.
That is
On Tue, Mar 05, 2013 at 08:28:15PM +0800, Paul Wise wrote:
> Is there anything we can add to debcheck or the PTS to encourage
> maintainers to help break these cycles by adding build profiles and or
> cross-compilation info?
It seems to be premature to add build profiles to packages, as the initia
(Resend, I accidentally sent this to the bug report.)
On Mon, Mar 04, 2013 at 10:07:30PM +0100, Nicolas Dandrimont wrote:
> (comments welcome on the long description, which looks like it needs
> some expanding)
Well yes, it could explain what on earth "Fabric files" are. I had to
look up the gith
Package: wnpp
Severity: wishlist
Owner: A Mennucc
* Package name: wfrog
Version : 0.8.2 + svn
Upstream Author : Jordi Puigsegur et al
* URL : http://code.google.com/p/wfrog/downloads/list
* License : GPL 3
Programming Lang: Python
Description : Web-bas
Hi,
while investigating on #699749 (which apparently affects many machines
using NM, but not all of them), I discovered that the interface for
ifupdown hooks has changed since squeeze.
>From the manpage:
When ifupdown is being called with the --all option, before doing any‐
thing
On Tue, Mar 05, 2013 at 05:04:26PM +0100, Lucas Nussbaum wrote:
> > Thus I have two remotes in my original repository:
> >
> > originssh://git.debian.org/git/pkg-lua/lua-lgi.git (fetch)
> > originssh://git.debian.org/git/pkg-lua/lua-lgi.git (push)
> > upstream git://github.com/pavou
Hi,
Quoting Simon McVittie (2013-03-05 16:54:00)
> This is useful information. Is there any way in which the maintainers of
> these packages can say "yes, we know, and here is where you break the cycle"
> without using unmerged dpkg features or breaking the freeze?
I'm afraid there is little one
On 03/05/2013 11:46, Bálint Réczey wrote:
> Please send error reports to the affected parties when executing or
> parsing a dak command file fails.
If you meet minimum requirements, dak will send an error message. But
dak and debianqueued only look at files that have a known extension
(e.g. *.dak-
On 05/03/13 at 16:40 +0100, Enrico Tassi wrote:
> I'm new to the art of packaging with git, and I found a little issue
> I'm unable to solve nicely.
>
> I'm in the usual situation, the package and the upstrem are under git.
> Thus I have two remotes in my original repository:
>
> origin ss
On 05/03/13 11:22, Johannes Schauer wrote:
> Since self-cycles in Debian are often unintuitive, maintainers might be
> unaware
> that the source packages they maintain are actually forming a self cycle.
This is useful information. Is there any way in which the maintainers of
these packages can sa
Hi,
Quoting The Wanderer (2013-03-05 15:35:37)
> You can build either one without a matching version of the other, but you
> won't get full functionality. In order to get the full functionality of both,
> from what I've been able to tell you need a minimum of three builds on every
> cross-matching
I'm new to the art of packaging with git, and I found a little issue
I'm unable to solve nicely.
I'm in the usual situation, the package and the upstrem are under git.
Thus I have two remotes in my original repository:
originssh://git.debian.org/git/pkg-lua/lua-lgi.git (fetch)
origin
On Tue, Mar 05, 2013 at 02:03:48PM +0100, Goswin von Brederlow wrote:
> On Sat, Feb 16, 2013 at 09:57:16AM +0100, Tzafrir Cohen wrote:
> > ...
> > I mentioned, I would prefer to keep those files out of my packaging
> > archive: they hardly change, anyway.
> >
> > So, what do you do with multi-tarb
At risk of making myself look like an idiot, I have a possibly contributory
question.
On 03/05/2013 06:22 AM, Johannes Schauer wrote:
Self-cycles can be divided into two classes:
1. a build dependency on a binary package the source package builds (the
simple case)
2. a build dependency
Hi,
Quoting Samuel Thibault (2013-03-05 14:57:04)
> For instance commons-beanutils is only producing arch:all packages (I don't
> understand why it has separate Build-Depends and Build-Depends-Indep BTW), so
> AIUI, ports don't need to build it and thus do not have to care about the
> dependency l
Hi,
Quoting Wouter Verhelst (2013-03-05 14:47:20)
> On Tue, Mar 05, 2013 at 02:41:51PM +0100, Johannes Schauer wrote:
> > The code generating that list is part of the debian bootstrap project [1]
> > and as such it would be a bug if architecture:all package were required to
> > be recompiled for t
Johannes Schauer, le Tue 05 Mar 2013 14:41:51 +0100, a écrit :
> Quoting Samuel Thibault (2013-03-05 13:41:12)
> > Maybe arch:all-only source packages should be shown in a different color:
> > AIUI these do not pose a problem for bootstrapping a new Debian port, since
> > one does not need to build
On Tue, Mar 05, 2013 at 02:41:51PM +0100, Johannes Schauer wrote:
> Hi,
>
> Quoting Samuel Thibault (2013-03-05 13:41:12)
> > Maybe arch:all-only source packages should be shown in a different color:
> > AIUI these do not pose a problem for bootstrapping a new Debian port, since
> > one does not n
Hi,
Quoting Samuel Thibault (2013-03-05 13:41:12)
> Maybe arch:all-only source packages should be shown in a different color:
> AIUI these do not pose a problem for bootstrapping a new Debian port, since
> one does not need to build the source package, and just pick up the existing
> _all.deb. The
On Thu, Feb 07, 2013 at 11:11:22PM -0400, Joey Hess wrote:
> Ben Hutchings wrote:
> > What I mean is that a changes file for a sourceful upload has
> > 'source' (and maybe some real architecture names) in the Architecture
> > field. Therefore 'source' cannot be assigned as the name of a real
> > a
On Sat, Feb 16, 2013 at 09:57:16AM +0100, Tzafrir Cohen wrote:
> ...
> I mentioned, I would prefer to keep those files out of my packaging
> archive: they hardly change, anyway.
>
> So, what do you do with multi-tarball packages? I keep a patched
> svn-buildpackage, for now.
You don't want the ex
Hello,
Johannes Schauer, le Tue 05 Mar 2013 12:22:46 +0100, a écrit :
> as of 2013-01-01: http://wiki.debian.org/DebianBootstrap/SelfCycles
Maybe arch:all-only source packages should be shown in a different
color: AIUI these do not pose a problem for bootstrapping a new Debian
port, since one doe
Is there anything we can add to debcheck or the PTS to encourage
maintainers to help break these cycles by adding build profiles and or
cross-compilation info?
--
bye,
pabs
http://wiki.debian.org/PaulWise
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "uns
Hi,
Since self-cycles in Debian are often unintuitive, maintainers might be unaware
that the source packages they maintain are actually forming a self cycle. I
therefore created a wiki page with the list of the 81 self-cycles in Debian Sid
as of 2013-01-01: http://wiki.debian.org/DebianBootstrap/S
Hi,
2013/3/5 Arno Töll :
> Ho Carlo,
>
> On 05.03.2013 07:42, Carlo Segre wrote:
>> 1. made a file called segre-0001.dak-commands with the following contents
>>
>> Action: dm
>> Fingerprint: 8CCC1BA8590FF029D17C708FC1BCD3C72AA28B6B
>> Allow: nexus
>
>
> You missed the header. While the "Uploader"
Package: wnpp
Severity: wishlist
Owner: Samuel Ortiz
* Package name: neard
Version : 0.10
Upstream Author : Samuel Ortiz
* URL : https://01.org/linux-nfc
* License : GPLv2
Programming Lang: C
Description : A Near Field Communication (NFC) daemon
neard
31 matches
Mail list logo
