> "Cameron" == Cameron Norman writes:
Cameron> Apparently this is a known issue, and another person has
experienced
Cameron> it: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760426
>>
>> That and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769499 are
>> closel
> "Cameron" == Cameron Norman writes:
>>> OK, so the system has syslog-ng installed. For what ever reason
>>> syslog-ng
>>> is not starting automatically, but starts manually by systemctl.
>>
>>> syslog-ng version 3.5.6-2
>>> systemd version 215-5+b1
>>
>> M
>>>>> "Raphael" == Raphael Hertzog writes:
Raphael> Hi Gergely,
Raphael> On Wed, 12 Nov 2014, Gergely Nagy wrote:
Raphael> When releasing a Debian package, the packager should create and
push
Raphael> a signed tag named `/`. For exam
> "Jonathan" == Jonathan Dowland writes:
Jonathan> On Wed, Nov 12, 2014 at 03:38:59PM +0800, Paul Wise wrote:
>> Personally I wouldn't use anything other than debian-only repos, at
>> least for those where I have a choice. I also actively avoid
>> contributing to packages that
> "Raphael" == Raphael Hertzog writes:
Raphael> Packaging branches and tags
Raphael> ===
[...]
Raphael> The Git repository listed in debian/control's `Vcs-Git` field
should
Raphael> usually have its HEAD point to the branch corresponding to the
R
>>>>> "David" == David L Craig writes:
David> On 14Nov10:2154+0100, Gergely Nagy wrote:
>> You do realize topic lists are public too, right?
David> Yes, but most Debian users don't even know about
David> them nor do they need to sin
> "David" == David L Craig writes:
David> On 14Nov10:2325+0900, Charles Plessy wrote:
>> With most of the work done on topic mailing lists, trolls lose the lever
effect
>> they have when feasting on debian-devel or debian-vote. Let's make our
project
>> stronger by reducing
Daniel Dickinson writes:
> On 10/09/14 02:52 PM, Noel Torres wrote:
>>
>> Yes. Why to install OpenVPN which might not work? aptitude will tell you
>> that
>> they are not coinstallable and the sysadmin will then have the option of
>> switching init system to a non default one, knowing what th
Package: wnpp
Severity: wishlist
Owner: Gergely Nagy
* Package name: adderall
Version : 0.1.2
Upstream Author : Gergely Nagy
* URL : https://github.com/algernon/adderall
* License : LGPL
Programming Lang: Hy
Description : a miniKanren implementation
Thibaut Paumard writes:
> Le 15/05/2014 10:55, Gergely Nagy a écrit :
>> You do realise we have one libc (sure, you can install *additional*
>> ones, but we have one libc the archive is compiled against), we have one
>> package manager (you can, of course, install rp
Thorsten Glaser writes:
>>. This
>>> is a perfectly fine job for a derivate or Pure Blend: to provide a
>>> polished system that serves one use case well.
>>
>>Proper integration certainly belongs into Debian or did we become a
>>supermarket:
>
> Proper integration of components: yes. That is the
Russ Allbery writes:
> Sune Vuorela writes:
>
>> Part of me wants to have KDE Plasma Desktop as the default workspace,
>> because it is completely awesome.
>
>> Other parts of me is happy that it is not the default because then we
>> don't have all sorts of weird wishes about "oh noes. networkma
Thomas Goirand writes:
> Actually, thinking about it a 2nd time, I think there would be a major
> drawback in delaying to Jessie +1. If we decide that sysv-rc goes away,
> then starting at the Jessie release, we don't have to care anymore about
> LSB header scripts. Meaning that we could write sy
Matthias Urlichs writes:
> Oh except that some people didn't, which causes problems for the systemd
> transition -- because init skript that are not skeleton-based don't know
> how to redirect itself to systemd …
Err, no. I have plenty of sysvinit scripts that work just fine with
systemd, and ar
"Francesco P. Lovergine" writes:
> On Thu, Feb 06, 2014 at 11:59:11AM +, Ian Jackson wrote:
>>
>> I think the best approach would probably be to automate the generation
>> of init scripts in debhelper.
>>
>
> Seconded. Using an auto-generated skeleton starting from a simple template
> woul
Thomas Goirand writes:
> What about exploring Ian Jackson's idea, which was to hack a debhelper
> that would generate things for multiple init systems?
Can I file RC bugs when that breaks horribly? (Because it will.)
I would suggest not going down that route, it only leads to pain and
suffering
The Wanderer writes:
> Also because when writing a parser, it's easier to determine the format
> (in terms of meaning and start/stop of each field) of a text file than
> it is of a binary one, when working without known-reliable
> documentation. (And I'm not willing to assume that I'll always hav
"Vitaliy Filippov" writes:
>> Here's a challenge then: Implement everything the journal does, without
>> using a binary format, and show us it's not only doable, but performs
>> similarly.
>>
>> I would first recommend you read up - and try! - what the journal has to
>> offer. It's not as simple
vita...@yourcmc.ru writes:
>> It is of course well-known that systemd developers like to make their
>> life more complicated and love to implement binary formats instead of
>> writing simple text parsers, just for the sake of having fun
>> programming
>> them, and absolutely not because they need
Petter Reinholdtsen writes:
> The reason I bring this up on debian-devel@ is twofold. First, I want
> to gather feedback on the idea. Will it work for your package, or are
> some more hooks needed?
With my syslog-ng upstream hat on: please, for the love of $deity, no!
It's bad enough having to
Package: wnpp
Severity: wishlist
Owner: Gergely Nagy
* Package name: syslog-ng-incubator
Version : git master (or whatever I call it by the time I
get there)
Upstream Author : BalaBit IT Security Ltd.
* URL : https://github.com/balabit/syslog-ng
Thorsten Glaser writes:
> On Tue, 5 Nov 2013, Paul Tagliamonte wrote:
>
>> > First of all, I do not agree Debian community is hurt because of
>> > split about init system,
>>
>> I disagree strongly. Please read through every flame thread over the
>> last 4 years and try to say this with a straig
Package: wnpp
Severity: wishlist
Owner: Gergely Nagy
* Package name: riemann-c-client
Version : 1.0.1
Upstream Author : Gergely Nagy
* URL : https://github.com/algernon/riemann-c-client/
* License : LGPL-3+
Programming Lang: C
Description : C language
Raphael Hertzog writes:
> On Tue, 03 Sep 2013, Luca Falavigna wrote:
>> 2013/9/3 Paul Wise :
>> > Reading Charles' mail I had a thought; how about accepting buggy
>> > packages (unless the issues make them non-distributable) and file RC
>> > and other bugs if there are DFSG or other issues?
>>
>
Peter Palfrader writes:
> On Sun, 01 Sep 2013, Steven Chamberlain wrote:
>
>> I can only recall one wishlist bug from DSA at the moment which is
>> #711247 requesting pflogd. I'd love to hear more wishlist kfreebsd
>> ideas from DSA.
>
> syslog-ng on kfreebsd doesn't properly reconnect to logser
Josselin Mouette writes:
> Le lundi 22 juillet 2013 à 10:45 +0200, Gergely Nagy a écrit :
>> systemd being installed does not mean it will be used as init. The
>> package happens to contain a few tools the GNOME Shell needs, that is
>> all, to the best of my knowl
Vincent Cheng writes:
> On Fri, Jul 19, 2013 at 9:35 AM, John Paul Adrian Glaubitz
> wrote:
>> On 07/19/2013 06:12 PM, Mathieu Parent wrote:
>>>
>>> As the recommended way to install systemd is using init= and not
>>> installing systemd-sysv, maybe the popcon "vote" count is the correct
>>> metr
John Paul Adrian Glaubitz writes:
> On 07/18/2013 09:15 AM, Thomas Goirand wrote:
>>
>> http://wiki.gentoo.org/wiki/Talk:Comparison_of_init_systems
>
>> "friendly upstream yes no NO YES"
>
> Really? You put something like this in a technical comparison chart?
A friendly upstream
Thomas Goirand writes:
> If OpenRC goes up to the shape I expect, it will have a huge advantage
> over systemd and Upstart: it will not be controversial,
If it would not be controversial, we wouldn't have this conversation
about whether it is worth it at all. Just saying.
--
|8]
--
To UNSUB
Marc Haber writes:
> On Thu, 30 May 2013 11:46:51 +0300, Riku Voipio
> wrote:
>>By switching early we can affect how a piece of software will evolve.
>
> This is the case with software that has a cooperative upstream.
> systemd's upstream is known not to be.
I never quite understood why people
Adam Borowski writes:
> On Thu, May 23, 2013 at 09:55:41AM +0200, John Paul Adrian Glaubitz wrote:
>> On 05/23/2013 06:56 AM, Thomas Goirand wrote:
>> > "As you may know, systemd is developed by a large amount of
>> contributors"
>>
>> How on earth does that contradict with the fact that 40%,
Steve Langasek writes:
> On Thu, May 23, 2013 at 09:11:55AM +0200, Gergely Nagy wrote:
>
>> Also, post-raring, systemd is available in Ubuntu aswell, and in some
>> cases, you can check for systemd at runtime, needing no modification to
>> the package *at all*.
>
>
Lucas Nussbaum writes:
> - there are 300+ upstart job files ready to be imported from Ubuntu
FWIW, there are a similar (if not more) number of systemd service files
we can look at and import from: Fedora, openSUSE, Arch and possibly a
few others too. (This I find to be a great strength of system
Thomas Goirand writes:
> On 05/23/2013 01:45 AM, Josselin Mouette wrote:
>> I understand it will be a pain for Ubuntu if Debian picks a different
>> init system. I don’t think this is relevant for the discussion, though.
>
> It might be very relevant for many of us that our package works on
> *bo
"brian m. carlson" writes:
>> I have no idea why people assume that a binary format means it can only
>> be processed with a special, proprietary tool. Binary simply means what
>> it means, binary and not text which means it's a more stream-lined and
>> machine-readable format as opposed to a tex
"brian m. carlson" writes:
> On Sat, May 11, 2013 at 10:08:21PM +0200, Josselin Mouette wrote:
>> This is utter bullshit and you should already know it. Systemd is much
>> more reliable as a whole than any other implementation. I have yet to
>> see a use case where it is not better.
>
> It is not
Clint Byrum writes:
>> Also if people thought that distributions are unneeded, then the
>> amount
>> of them would reflect that, or start decreasing, which I'm not seeing.
>> Distributions will exist as long as there's FLOSS, because by its
>> decentralized nature, there's no single coordination
Ian Jackson writes:
> Gergely Nagy writes ("Re: No native packages?"):
>> There are two native packages I maintain, and I've yet to hear a good
>> reason for making either of them non-native. Making it harder and much
>> much more inconvenient for downstre
Roland Mas writes:
> Gergely Nagy, 2013-01-28 09:44:18 +0100 :
>
> [...]
>
>> By harmful side effects, I mean two things:
> [...]
>> - Patches not separated
>
> Not quite true. You can still have debian/patches/* and apply them at
> build-time (dpatch or
Wouter Verhelst writes:
> On Mon, Jan 28, 2013 at 09:44:18AM +0100, Gergely Nagy wrote:
>> Wouter Verhelst writes:
>>
>> > On Sun, Jan 27, 2013 at 07:16:44PM +0100, Jakub Wilk wrote:
>> >> Dmitrijs Ledkovs wrote on his blog[0]:
>> >>
>> &g
Tollef Fog Heen writes:
> ]] Gergely Nagy
>
>> No, not really. I don't really care what tools one uses, as long as the
>> result is reasonably easy *and* reliable to work with. Since VCS can be
>> stale, and quite often does not include neither NMUs, nor backport
Philip Hands writes:
> Gergely Nagy writes:
> ...
>> We have tools that make it easy to create upstream tarballs from an SCM
>> repo. Git has git archive, gitpkg and possibly other tools make it very
>> easy to create upstream tarballs: so much so, that it means nothing
Wouter Verhelst writes:
> On Sun, Jan 27, 2013 at 07:16:44PM +0100, Jakub Wilk wrote:
>> Dmitrijs Ledkovs wrote on his blog[0]:
>>
>> >Generally if software is useful in Debian Project it can be useful
>> >for other debian-like and unlike projects. In particular native
>> >packages do not offer
Arno Töll writes:
> Hi,
>
> On 27.01.2013 19:32, Gergely Nagy wrote:
>> There are two native packages I maintain, and I've yet to hear a good
>> reason for making either of them non-native.
>
> Not knowing your use cases in particular, it would often be good enou
Jakub Wilk writes:
> Dmitrijs Ledkovs wrote on his blog[0]:
>
>> Generally if software is useful in Debian Project it can be useful
>> for other debian-like and unlike projects. In particular native
>> packages do not offer the same patching flexibility as 3.0 (quilt),
>> thus forcing downstream
Alexey Eromenko writes:
> User error? Huh ?
It is, I'm afraid.
> No ! This is a Debian Bug !
No, it is not.
> Debian clearly says: "File does not exist", while in fact it DOES
> EXIST.
It does not. However, the file the message is referring to is not the
file you think it refers to: it is mi
"Andrej N. Gritsenko" writes:
> Hello!
>
> Gergely Nagy has written on Wednesday, 21 November, at 10:29:
>>Matthias Klumpp writes:
>
>>> For syslogd, systemd provides journald for those who want to use it,
>>> but the Journal is no dependency of
Matthias Klumpp writes:
> For syslogd, systemd provides journald for those who want to use it,
> but the Journal is no dependency of systemd.
Wrong. You can't have any recent systemd without the Journal, and
'legacy' syslogds are piggybacking on /run/systemd/journal/syslog, where
the journal for
Bart Martens writes:
>> > I think that sufficient DDs will review the ITOs. Note that most work is
>> > already done by the ITO submitter. Sponsoring a package at mentors
>> > ("review
>> > other peoples work") is, in my opinion, much more work than reading an ITO
>> > and
>> > sending an ACK
Steve Langasek writes:
>> > > No, it makes the process based on *consensus*, which is a minimum
>> > > requirement.
>
>> > It also means that the salvager has to do more work.
>
>> I expect the cc to debian-qa to draw sufficient DD's attention. And the
>> ACKs are about agreeing on marking a pac
Ian Jackson writes:
> Whether a package is in need of greater attention is not a hard and
> fast objective thing. It's to a large part subjective. Perhaps the
> maintainer thinks it's more or less fine, or at least low enough
> priority that the problems are tolerable.
Then the maintainer has
Bart Martens writes:
> On Wed, Oct 24, 2012 at 01:58:16PM +0200, Gergely Nagy wrote:
>> Steve Langasek writes:
>>
>> > On Tue, Oct 23, 2012 at 02:40:39PM +0200, Stefano Zacchiroli wrote:
>> >> > 4. When/if consensus has been reached, the package can
Steve Langasek writes:
> On Wed, Oct 24, 2012 at 01:58:16PM +0200, Gergely Nagy wrote:
>> > I disagree on this point. If you can't get anyone to ack that you should
>> > go
>> > ahead with the orphaning, then the system is not working as designed and
>>
Steve Langasek writes:
>> So, what will you do if:
>> - previous maintainer goes MIA
>> - Somebody wants to hija^W salvage the package and starts the procedure
>> - Nobody votes for this to happen...
>
>> Should we then leave the package forever unmaintained?
>> I don't think this is reasonable..
Steve Langasek writes:
> On Tue, Oct 23, 2012 at 02:40:39PM +0200, Stefano Zacchiroli wrote:
>> > 4. When/if consensus has been reached, the package can be orphaned by
>> >retitling and reassigning the ITO bug accordingly.
>
>> I fear a bit the situation "nobody care enough to comment", being
Tollef Fog Heen writes:
> ]] Jakub Wilk
>
>> What makes a buildd more secure than a machine of J. Random Developer?
>
> It has a smaller attack surface due to few users, firewalls, few
> packages installed, nobody using it for browsing the web, etc.
We seem to be forgetting, that the real advan
Lucas Nussbaum writes:
> On 11/10/12 at 05:50 +, Bart Martens wrote:
>> | Anyone can mark a package as orphaned after the following steps have
>> been
>> | completed : Someone submits an "intent to orphan" (ITO) in the bts with
>> an
>> | explanation of why he/she thinks that the p
Paul Tagliamonte writes:
> If any DM asks me to, and they can show they've made uploads (with
> DMUA) before this announcement for that package, and that they've not
> broken things in a gnarly gnarly way (and if their sponsor is VAC,
> MIA or otherwise not here), I don't think I'd have any probl
Arno Töll writes:
> On 22.09.2012 10:06, Ansgar Burchardt wrote:
>> We are using this opportunity to clean up the "DM database" and will not
>> convert any of the DMUA flags to the new format, but two months ought to
>> be enough for any active DM to ensure their sponsor DDs have set the new
>> p
Philipp Kern writes:
> On Mon, Aug 20, 2012 at 10:32:07AM +0200, Gergely Nagy wrote:
>> If neither upstream, nor porters care about a particular package, that
>> means there are very little use of having it on that port, and one
>> should consider changing the Architectur
Charles Plessy writes:
> Le Sun, Aug 19, 2012 at 11:13:23PM +0200, Gergely Nagy a écrit :
>> Michael Biebl writes:
>>
>> > If those ports need a GR to silence any criticsm regarding those ports,
>> > then something is going seriously wrong.
>>
>&g
Michael Biebl writes:
> If those ports need a GR to silence any criticsm regarding those ports,
> then something is going seriously wrong.
I've yet to see said criticism.
--
|8]
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Conta
David Given writes:
> Thomas Goirand wrote:
> [...]
>> Exactly what do you need from sbin as a user?
>
> I use stuff from sbin as user all the time. A quick glance at /sbin
> shows these commands that I use on a regular basis:
>
> blkid
> fdisk
> all the fscks
> all the mkfss
> hdparm
> ifconfig
Miles Bader writes:
> Gergely Nagy writes:
>> if upstream considers a package a core part of a platform,
>> recommends *is* wrong.
>
> Er, no.
>
> Upstreams are not infallible, and are often quite fallible...
>
> Upstream's "view" is a good _defa
Gergely Nagy writes:
>> Please don't forget that a Recommends will pull in packages in all but
>> unusual installations :)
>
> But also keep in mind, that once a package is installed, adding new
> recommends will not pull those new things in on an upgrade.
I&#x
Andrei POPESCU writes:
> On Jo, 12 iul 12, 17:44:52, Gergely Nagy wrote:
>>
>> > Then some time later during upgrade it'll upgrade all packages
>> > but will not install N-M; at the same time it'll install
>> > new package that was added to Reco
Andrei POPESCU writes:
> On Jo, 12 iul 12, 12:10:29, Gergely Nagy wrote:
>>
>> Erm, how have I broken my system? I did not. (Turning Install-Recommends
>> off is definitely not breaking my system, FYI.)
>
> It means you are running with a non-default configuration an
Andrei POPESCU writes:
> On Jo, 12 iul 12, 15:46:05, Gergely Nagy wrote:
>>
>> X) Downgrade stuff to recommends
>>
>>
>> I do not consider this a solution, for reasons explained elsewhere,
>> where my main concer
Tollef Fog Heen writes:
> ]] Gergely Nagy
>
>> Instead of fighting for Recommends, which would break your system in
>> various interesting ways later on[1], there's a third solution: noone
>> stops anyone from uploading a gnome-minimal package, which depends
Wouter Verhelst writes:
> On Tue, Jul 10, 2012 at 04:18:17PM +0200, Gergely Nagy wrote:
>> "Eugene V. Lyubimkin" writes:
>>
>> > On 2012-07-10 15:32, Josselin Mouette wrote:
>> >> Le mardi 10 juillet 2012 à 17:38 +0900, Miles Bader a écrit :
>
FTR: Please don't CC me on list mail. I'm tired of setting M-F-T.
Tomasz Rybak writes:
> Dnia 2012-07-12, czw o godzinie 15:46 +0200, Gergely Nagy pisze:
>> Tomasz Rybak writes:
>>
>> > At first I thought it was a joke. But no, you really suggest that
>
Tomasz Rybak writes:
> At first I thought it was a joke. But no, you really suggest that
> everyone who wants to have up-to-date desktop environment
> but without few packages (e.g. N-M or GDM) needs to create own package,
> own local repository, and looks into it every time there is upgrade
> to
Thibaut Paumard writes:
> Le 12/07/12 11:06, Gergely Nagy a écrit :
>> Lets consider another case! Suppose I have Install-Recommends turned on,
>> and install a theoretical meta package, that has half of its stuff in
>> recommends, because they're not strictly nec
Andreas Tille writes:
>> It's a meta-package, that pulls in a platform. If I install it, I want
>> the full platform, always. That's about it. If I install mono-complete,
>> I want the whole bloody thing, always.
>
> I think the attempt to ensure something always is not reasonable because
> if th
Abou Al Montacir writes:
>> As with any package available in Debian: Just don't install it if you do
>> not like what the package does!
>>
>> It really is that simple!
>
> I think that we really do not have the same understanding of
> metapackage. You clearly want them strict and non flexible,
Andrei POPESCU writes:
> On Mi, 11 iul 12, 14:41:50, Gergely Nagy wrote:
>> Andrei POPESCU writes:
>> >
>> > Depending on how you do the package selection on your next installation
>> > you might end up with rsyslog, but without logrotate[1].
>>
&g
Steve McIntyre writes:
> Gergely wrote:
>>Henrique de Moraes Holschuh writes:
>>
>>> IMO, metapackages should "depend" on the absolutely required stuff (and many
>>> times that will be the empty set), "recommend" the rest, and maybe even
>>> "suggest" fringe packages. This achieves maximum usab
"Eugene V. Lyubimkin" writes:
> On 2012-07-11 14:33, Gergely Nagy wrote:
>> "Eugene V. Lyubimkin" writes:
>>
>> > Moreover, despite me understanding the picture, I still
>> > has no clean, safe and documented way to do what I'
Noel David Torres Taño writes:
>> Yet, we try to not diverge much from upstream, and maintain a good
>> relationship with them. If they consider it core, so can we. Those who
>> want to hand-pick parts of a meta package, can do so, we do not forbid.
>
> If we want to be user friendly, it is not a
Thibaut Paumard writes:
>> That also achives maximum annoyance, because if I want the full
>> platform, I'll have to go recommends/suggest hunting. (No, I'm
>> *not* going to turn on install-recommends.)
>
> You don't want to turn on install-recommends, but you are happy with
> installing a load
Noel David Torres Taño writes:
>> Well, in case of GNOME, upstream considers n-m to be part of the core
>> system, to the best of my knowledge. If upstream does so, so should we.
>
> No. That's why we have our own distribution instead of just a collection of
> unpatched packages compiled from so
Andrei POPESCU writes:
> On Ma, 10 iul 12, 18:43:03, Gergely Nagy wrote:
>>
>> During the past ~14 years I've been using Debian with that setting
>> turned off, nothing ever broke on my systems because of this setting. If
>> it does, then I'll consider t
Henrique de Moraes Holschuh writes:
> IMO, metapackages should "depend" on the absolutely required stuff (and many
> times that will be the empty set), "recommend" the rest, and maybe even
> "suggest" fringe packages. This achieves maximum usability for more
> usecases, and malfunctions only in
"Eugene V. Lyubimkin" writes:
> Moreover, despite me understanding the picture, I still
> has no clean, safe and documented way to do what I'd want in case the
> package maintainer chosed Depends.
You have: install the pieces you want by hand. That's at least clean and
safe. I do not think it is
Nikolaus Rath writes:
> Gergely Nagy writes:
>> For the cases where one wants to have most of the stuff installed that
>> the meta-package would pull in, but not all, solutions already exist.
>
> What solutions do you mean?
Installing the pieces one wants by hand, for one.
Nikolaus Rath writes:
> Gergely Nagy writes:
>> But, to cut the story short, attached to this mail is a script you can
>> use to take any metapackage, and remove (or demote) any of its
>> dependencies. It echoes a control-file thingy, combining it with equivs
>> is
Sune Vuorela writes:
> On 2012-07-10, Gergely Nagy wrote:
>> No. Only if installing recommends is turned on, which cannot be
>> guaranteed.
>
> There is many ways to break your system. turning off installation of
> recommends is one of them.
During the past ~14 year
"Eugene V. Lyubimkin" writes:
> On 2012-07-10 18:10, Jonas Smedegaard wrote:
>> The very purpose of a meta-package is to _ensure_ that a certain set of
>> packages is installed, not just recommend them: All (not only most)
>> users of that package need all its dependencies satisfied
>
> My defi
"Eugene V. Lyubimkin" writes:
> On 2012-07-10 16:18, Gergely Nagy wrote:
>> But the purpose of the meta-package is to pull stuff in. Depends does
>> that, Recommends does not, therefore Recommends is not appropriate for
>> the task.
>
> Surely Recomm
"Eugene V. Lyubimkin" writes:
> On 2012-07-10 15:32, Josselin Mouette wrote:
>> Le mardi 10 juillet 2012 à 17:38 +0900, Miles Bader a écrit :
>> > What's wrong with Recommends: in that case? It seems to perfectly
>> > match the "makes life easier for > > XXX>" scenario you describe.
>>
>> Reco
"Theodore Ts'o" writes:
> P.S. One of the things I'm thinking about doing is writing a script which
> automatically generates the debian/patches directory from the git
> repository. So when I specify the base release (i.e., v1.42.4), it will
> do something like git format-patch, but in a debian/
Ansgar Burchardt writes:
> On 06/15/2012 11:33 AM, Thomas Goirand wrote:
>> Yeah, a hook of any sorts is ok for me. The get-vcs-source in debian/rules
>> seems quite ok to me. Should debcheckout be modified to call it? It's part
>> of devscript, do you think it's ok if I submit a wishlist bug rep
Thomas Goirand writes:
> On 06/15/2012 12:03 AM, Cyril Brulebois wrote:
>> Anyway, here's what I've been doing for our 150+ X packages:
>>
>> $ cat xserver-xorg-video-ati.git/debian/watch
>> #git=git://anongit.freedesktop.org/xorg/driver/xf86-video-ati
>> version=3
>> http://xorg.freedesktop.org
Gregor Jasny writes:
> When one tries to fix a FTBFS bug a look into the upstream VCS is
> often helpful. Sometimes a link to browse them is easily found on the
> homepage linked from the PTS page. But often these links are deeply
> buried in the linked website.
>
> What I'd like to see in the De
Ian Jackson writes:
> So for example, DDs have enormous theoretical power but there are
> strong and well documented social controls on how they should exercise
> that. I think as a matter of principle that the same principle should
> apply to DMs: it is easy to remove a misbehaving DM from Uplo
Bernd Zeimetz writes:
> Which bad things happened that we have to change the current process?
As far as I see, it's more about "what good things didn't happen" why we
have to change the process.
That is also addresses a few corner cases that could've gone bad, but
never did is a side-effect.
-
Thomas Goirand writes:
> By the way, do other think that, even in this case, I should keep the
> changes
> as minimum as possible? Or is it ok, considering that all of our
> toolsets have
> changed since the last upload (eg: we now have pkg-php-tools and dh 8
> sequencer), that we do a bit more c
"Daniel Leidert" writes:
> Hi,
>
> Our bug tracker contains items for packages, which do (not longer)
> exist. What should happen to them? I see, that it might be a good idea
> to keep them for the case, a package is re-introduced. But this might
> happen only for a few packages. Most of them got
Chris Knadle writes:
> On Wednesday, May 16, 2012 06:38:49, Adam Borowski wrote:
>> On Tue, May 15, 2012 at 10:10:28AM +0100, Jon Dowland wrote:
>> > On Tue, May 15, 2012 at 03:17:17PM +0900, Norbert Preining wrote:
>> > > No, I hereby start saying good by to 3.0
>> >
>> > I'm hoping we can revi
Josselin Mouette writes:
> Le dimanche 13 mai 2012 à 20:00 +0200, Gergely Nagy a écrit :
>> > There is a huge difference between gconf, for which you can set one
>> > specific setting in /etc, overriding the default in /usr (and in a way
>> > that will not break
1 - 100 of 246 matches
Mail list logo
