Russell Coker writes:
> On Sun, 18 Dec 2011, Josselin Mouette wrote:
>> > Doing this has many advantage. Like, if your laptop has to unexpectedly
>> > reboot (like when you inadvertently removed power cord when batteries
>> > were not plugged, which happens often in real life), having separated
Josselin Mouette writes:
> Le samedi 17 décembre 2011 à 17:42 +0800, Thomas Goirand a écrit :
>> I do recommend a separate /usr to anyone. It's *not* safe to say that,
>> and I know many people that agree with me. To me, it has, and still is,
>> the best choice. You have no rights to arbitrar
Steve Langasek writes:
> On Fri, Dec 16, 2011 at 07:32:35PM +0100, Michael Biebl wrote:
>> On 16.12.2011 18:38, Joey Hess wrote:
>> > Christian PERRIER wrote:
>> >> I'm inclined to follow this advice and would indeed propose that the
>> >> "atomic" partman-auto recipe is kept, however without a s
Josh Triplett writes:
> On Fri, Dec 16, 2011 at 12:13:55PM +0100, Goswin von Brederlow wrote:
>> Josh Triplett writes:
>> > Russ Allbery wrote:
>> >>Josh Triplett writes:
>> >>> In all of the recent discussions about separate /usr partitions, m
Josh Triplett writes:
> Russ Allbery wrote:
>>Josh Triplett writes:
>>> In all of the recent discussions about separate /usr partitions, most
>>> people seem to acknowledge them as unusual, special-purpose
>>> configurations, even those who use them. To the extent they have a use
>>> at all, th
Gergely Nagy writes:
> Josselin Mouette writes:
>> Well, thanks for making my point. Implementing these (useful) features
>> in debhelper would be less pain to write and less eyesore for looking at
>> the implementation.
>
> Perhaps. But the executable thing is what is in debhelper, not the
> va
Roger Leigh writes:
> On Wed, Dec 14, 2011 at 12:53:24PM -0500, Zachary Harris wrote:
>> I could be wrong, but my (admittedly stereotyped) impression of the
>> standard use cases is that if you've got someone who DOES want to mount
>> /usr separately from "/" (e.g. over NFS or because of a sele
Russ Allbery writes:
> Zachary Harris writes:
>
>> My understanding of the FHS would be that if a library is a dependency
>> of a binary in /bin or /sbin, then such library belongs in /lib, not
>> /usr/lib. (If for some reason the library is also desired in /usr/lib
>> then a sym link from /lib
Thomas Koch writes:
> Hi,
>
> I just made a fool of myself on the simple-build-tool list by claiming that
> Debian would build scala without scala. I only checked debian/rules and
> debian/control and since scala is in main, I assumed that I must be right.
>
> However scala comes with a bytecode
Joey Hess writes:
> Gergely Nagy wrote:
>> At the moment, I have something that works like this:
>>
>> ,
>> | #! /usr/bin/dh-exec-install
>> | # The next one will simply echo it back to dh_install
>> | source-file /dest-dir/
>> |
>> | # This one will copy the file itself, following similar h
Reinhard Tartler writes:
> On Mo, Dez 12, 2011 at 05:36:41 (CET), Karl Goetz wrote:
>
> [...]
>
>>> The initramfs on the other hand is made to fit. So if /usr isn't on a
>>> networking filesystem (NFS) then you won't get networking stuff in the
>>> initramfs. No raid then mdadm isn't included. No
Gergely Nagy writes:
> Goswin von Brederlow writes:
>
>>> So, in this case, the difference is negligible, both can be trivially
>>> understood.
>>>
>>> However, it gives more flexibility to the maintainer, to do more complex
>>> stuff, if s
Darren Salt writes:
> I demand that Stephan Seitz may or may not have written...
>
>> On Wed, Dec 07, 2011 at 11:34:34AM +0100, Marco d'Itri wrote:
>>> Actually, Red Hat's goal *is* to support a separate /usr, they just want
>>> to have the initramfs mount it.
>
>> But as was seen in the last dis
Russ Allbery writes:
> Goswin von Brederlow writes:
>
>> But there is no way to find bugs taged help given a skillset. So unless
>> you specifically think "Lets fix something in grub today" and go looking
>> for grub bugs tagged help you never find them.
>
Russ Allbery writes:
> Goswin von Brederlow writes:
>
>> Maybe we also need a different "need help" system where it is easier to
>> find something fun and usefull to do on a rainy day.
>
>> Something where RFHs for small jobs can be added with some tags for
Russ Allbery writes:
> Tollef Fog Heen writes:
>
>> I've always (well, since they were introduced) thought about the RFH
>> bugs as either «we're now starting a team effort to fix up $package,
>> please come and help» and more commonly: «I'm stuck maintaining this
>> package with a mostly non
Stephan Seitz writes:
> On Fri, Dec 09, 2011 at 08:21:30AM +0100, Goswin von Brederlow wrote:
>>As I mentioned I have a bug open (in the grml bug tracker) about
>>providing a grml.deb. That would install an image in /boot and add
>>itself to the bootloader. The small gr
Peter Samuelson writes:
> [Kees Cook]
>> This doesn't work with source-format-1 packages without adding
>> "chmod" lines for the scripted debhelper config files in the rules
>> file. Perhaps this isn't a big deal since we should all be using
>> source-format-3 anyway.
>
> We should? I prefer to
Gergely Nagy writes:
> Goswin von Brederlow writes:
>
>>> Compared to writing overrides, it's less effort. Compared to just
>>> writing the variable and expecting it to work, it's two commands more. I
>>> believe that's not much.
>>>
>
Jonathan Nieder writes:
> Hi,
>
> Just a quick side-note.
>...
> The main technical difficulty seems to be platforms where it is common
> to boot without an initramfs (for example, if it is hard to
> reconfigure the bootloader and the bootloader is already set up to use
> a plain kernel).
>
> Hop
m...@linux.it (Marco d'Itri) writes:
> Some people also argued that they would be more comfortable with a
> smaller root file system which can act as a rescue system, but I am
> not sure about which tools they would miss from an initramfs with
> busybox and fsck.
lvm, dmsetup, mdadm, crypto stuff
Gergely Nagy writes:
> Thomas Goirand writes:
>
>> Disclaimer: I didn't write any multiarch packaging (yet).
>>
>> The incentive for doing all this seems to be multiarch. Why
>> instead don't we have a mechanism to have variables in
>> debian/*.install instead, or a dh_helper to move things to
>
Bernd Zeimetz writes:
> On 12/07/2011 11:47 PM, Josselin Mouette wrote:
>> Now that weâve made incredible progress in terms of obfuscation, Iâd
>> appreciate if we could have a working solution that does not require
>> scripting for the most trivial operations. So what remains?
>> * Co
Gergely Nagy writes:
> Steve Langasek writes:
>
>> On Thu, Dec 08, 2011 at 10:07:12PM +0100, Gergely Nagy wrote:
>>> Kees Cook writes:
>>
>>> > Which means I can't use DEB_HOST_MULTIARCH in the config-scripts,
>>> > unfortunately.
>>
>>> Not to worry! dh-subst will be coming in a day or two (+
Igor Pashev writes:
> Goswin, thanks for the explanation.
> Now I'm inclined to move all to /usr :-)
We live to serve. :)
I'm kind of undecided. I know eventualy this will just work and have
eliminate all those "Hey, I have a strange setup and xyz needs to be in
/ for this" bugs. But I also am
Arno Töll writes:
> Hello,
>
> On 08.12.2011 10:44, Goswin von Brederlow wrote:
>> Or for the more general case:
>>
>> override_dh_auto_install:
>> debian/libfoo.my-install-script
> [..]
>
>> This new feature stinks of black-box magic that w
Stephan Seitz writes:
> On Thu, Dec 08, 2011 at 10:25:07AM +0100, Goswin von Brederlow wrote:
>>I guess mounting /usr is no more complicated than mounting / in
>>initramfs. Finding out what modules and software is needed for that
>>should be the same code as for /.
>
>
Arno Töll writes:
> Your own script-fu in debian/rules or external scripts isn't exactly the
> next best thing to read and learn how a foreign package works and there
> /are/ use cases where dh_install isn't flexible enough to deal with the
> problem by using the possibilities you had before. Re
Don Armstrong writes:
> On Wed, 07 Dec 2011, Josselin Mouette wrote:
>> So, to sum it up. Before, you would do in debian/rules:
>> sed s/@DEB_HOST_MULTIARCH@/${DEB_HOST_MULTIARCH}/
>> debian/libfoo.install.in > debian/libfoo.install
>>
>> Now, you will do in debian/foo.install:
>>
Igor Pashev writes:
> 07.12.2011 04:43, Marco d'Itri пиÑеÑ:
>> http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=12a362be5c1982f80dbfb75bda070208a2c99cdf
>>
>> Discuss.
>>
>
> I don't see any reason to move all into /usr from /,
> and make initrd for minimal system:
>
> Making
m...@linux.it (Marco d'Itri) writes:
> On Dec 07, Goswin von Brederlow wrote:
>
>> Give everyone at least 10 years headstart to migrate existing systems
>> away from having a seperate /usr partition and for people to stop making
>> a seperate /usr on new installs.
&
Philip Hands writes:
> On Wed, 7 Dec 2011 09:00:35 +, Simon McVittie wrote:
>> On Wed, 07 Dec 2011 at 01:43:34 +0100, Marco d'Itri wrote:
>> > http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=12a362be5c1982f80dbfb75bda070208a2c99cdf
>> >
>> > Discuss.
>>
>> As far as I can ma
m...@linux.it (Marco d'Itri) writes:
> http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=12a362be5c1982f80dbfb75bda070208a2c99cdf
>
> Discuss.
>
> --
> ciao,
> Marco
Give everyone at least 10 years headstart to migrate existing systems
away from having a seperate /usr partition and
Joerg Jaspert writes:
> metapackages, which is for metapackages so that apt can do special
> handling on them.
On IRC Joerg mentioned that transitional packages could/should also go
to the metapackages section.
The reasoning being that both metapackages and transitional packages
s
Wolodja Wentland writes:
> Hello,
>
> we are seeing an increasing number of users in #debian-next asking about FTBFS
> bugs that are reported by apt-listbugs during upgrades. Most of those users
> are not familiar with acronyms such as FTBFS or if these bugs apply to their
> setup.
>
> The underl
Philipp Kern writes:
> On 2011-12-02, Marc Haber wrote:
>> I also support this and think it is a really good idea. But please
>> keep x.y.z-1 around and easily accessible when x.y.z is released.
>
> You can jigdo any old CD image. It's just netinst that breaks.
> Normal CD images will continue
Martin Wuertele writes:
> * Paul Wise [2011-11-29 03:33]:
>
>> On Tue, Nov 29, 2011 at 9:04 AM, Steve Langasek wrote:
>>
>> > Â - Custom patch commands, as already discussed. Â Yes, we should get rid
>> > of
>> > Â them, but that doesn't make it easy to convert them.
>> >
>> > Â - Conditional
Alexander Wirt writes:
> Jon Dowland schrieb am Montag, den 28. November 2011:
>
>> On Mon, Nov 28, 2011 at 12:54:57PM +0100, Alexander Wirt wrote:
>> > And I still like the "never touch a running system" approach. If dpatch
>> > works
>> > without problems, why deprecate it?
>>
>> One reason i
Thomas Koch writes:
> Hi,
>
> I'm currently discussing with Jitsi[1] what they could do to make packaging
> feasible. On the java site they'll now probably use Ivy to document and
> manage
> their java dependencies.
>
> But they also have a lot of dependencies to C libraries. These are curren
Matthias Klose writes:
> On 11/19/2011 11:42 PM, Ben Hutchings wrote:
>> The i386 architecture was the first in Linux and in Debian, but we have
>> long since dropped support for the original i386-compatible processors
>> and now require a minimum of a 486-class processor.
>>
>> I think it is ti
Adrian Knoth writes:
> On Sun, Nov 20, 2011 at 08:40:47AM +0100, Raphael Hertzog wrote:
>
> Hi!
>
>> > 6. DM&P/SiS Vortex86 and Vortex86SX. These supposedly have all
>> >586-class features except an FPU, and we could probably keep FPU
>> >emulation for them.
>>
>> FWIW, I do run Debian
Peter Samuelson writes:
> [Jakub Wilk]
>> If a package is marked as "Multi-Arch: same", files with the same
>> name have to be (byte-to-byte) identical across all architectures.
>> Unfortunately, not all packages obey this requirement.
>
> [libsvn-java 1.6.17dfsg-2+b1]
> usr/share/java/sv
Guillem Jover writes:
> Hi!
>
> On Sat, 2011-11-19 at 22:42:11 +, Ben Hutchings wrote:
>> The i386 architecture was the first in Linux and in Debian, but we have
>> long since dropped support for the original i386-compatible processors
>> and now require a minimum of a 486-class processor.
>>
Goswin von Brederlow writes:
> Steve McIntyre writes:
>
>> Marc Haber wrote:
>>>On Thu, 17 Nov 2011 20:26:33 +, Ben Hutchings
>>> wrote:
>>>>
>>>>I can't imagine why you would expect this to work.
>>>
>>>I wou
Hi,
this isn't quite on topic and you are just the last in a long list of
"bits from xyz" but I think it has to be said: Thanks for keeping us
informed.
I think this year has been the most informative ever, at least that is
how it feels to me. So to you and all the others please do keep up the
"b
Steve McIntyre writes:
> Marc Haber wrote:
>>On Thu, 17 Nov 2011 20:26:33 +, Ben Hutchings
>> wrote:
>>>
>>>I can't imagine why you would expect this to work.
>>
>>I wouldn't. The site was just surprised by the point release and did
>>notice the deployment failure well before the announcemen
Marc Haber writes:
> On Fri, 18 Nov 2011 19:48:24 +, Ben Hutchings
> wrote:
>>On Fri, Nov 18, 2011 at 05:59:59PM +0100, Marc Haber wrote:
>>> On Thu, 17 Nov 2011 20:43:32 +, "Adam D. Barratt"
>>> wrote:
>>> >but
>>> >the kernel team have been very good in the past about fixing such thin
Ben Hutchings writes:
> On Thu, Nov 17, 2011 at 09:08:17PM +0100, Marc Haber wrote:
>> On Thu, 17 Nov 2011 11:00:26 +0100, Adam Borowski
>> wrote:
>> >For example: you download the current point release, burn it to a CD
>> >preparing to install a bunch of servers the next day... then suddenly
>
Russell Coker writes:
> On Wed, 16 Nov 2011, Goswin von Brederlow wrote:
>> With a filesystem it will write the dirty buffers to disk in the
>> background and then drop the clean pages from the cache quite
>> consistently. This leaves the code involved with moving the mouse
Adam Borowski writes:
> On Thu, Nov 17, 2011 at 06:39:28AM +, Ben Hutchings wrote:
>> On Thu, 2011-11-17 at 04:10 +, Cherukuri, Shravan Kumar wrote:
>> > I have an image of Debian-502-i386-netinst-iso which I burned to a CD
>> > and tried to install the OS.
>>
>> Old netinst images gener
Salvo Tomaselli writes:
>> While amazon.com "cloud" may have small RAM and large disks, many
>> mainframes are opposite (ie, IBM big blue, japan's world simulator). And
>> many new PCs may become that way: no spin :) Maybe not!
>
> I think we are focusing a bit too much on super expensive compu
Carlos Alberto Lopez Perez writes:
> On 16/11/11 11:37, Goswin von Brederlow wrote:
>> Assuming you have increased your SWAP by the size of the tmpfs to
>> compensate for /tmp now using RAM+SWAP you can only ever get that effect
>> in cases where the OOMKiller would have a
Chow Loong Jin writes:
> On 16/11/2011 22:45, Salvo Tomaselli wrote:
>>
>>> Given that any burning software can (approximately) determine what size the
>>> ISO file will be, it should really not start to write it in /tmp when the
>>> /tmp size is not big enough (which the software can also check
Richard writes:
> On Wed, 16 Nov 2011 13:21:47 +0100
> Didier Raboud wrote:
>
>> Salvo Tomaselli wrote:
>>
>> >> I think the problems you describe are quite uncommon. Yes, there are use
>> >> cases where tmpfs for /tmp isn't the best solution but I think most
>> >> people do not place 1.2GB fil
Salvo Tomaselli writes:
>> I think the problems you describe are quite uncommon. Yes, there are use
>> cases where tmpfs for /tmp isn't the best solution but I think most
>> people do not place 1.2GB files in their /tmp and benefit greatly from
>> tmpfs.
>
> I thought DVD burners were quite commo
Roger Leigh writes:
> On Wed, Nov 16, 2011 at 11:56:40AM +0100, Goswin von Brederlow wrote:
>> Roger Leigh writes:
>>
>> > As touched on in the bug report, I think that being able to store
>> > 1.2GiB on /tmp is an unrealistic expectation. To qualify, I mea
Chow Loong Jin writes:
> On 16/11/2011 18:12, Goswin von Brederlow wrote:
>> [...]
>> How do you intend to build that fake lib?
>>
>> I guess it comes down to getting a list of symbols on an existing
>> architecture (or from the symbols file?), creating a &q
Roger Leigh writes:
> On Sat, Nov 12, 2011 at 10:24:00PM +0100, Bastien ROUCARIES wrote:
>> Recently debian put /tmp under tmpfs.
>>
>> Even if it increase reponsivness under desktop, it ruin completly
>> sciene and imaging software that do some off loading on /tmp.
>>
>> For instance using gsc
Ben Hutchings writes:
> On Sun, 2011-11-13 at 04:04 +0100, Carlos Alberto Lopez Perez wrote:
>> On 12/11/11 23:25, Josselin Mouette wrote:
>> > Le samedi 12 novembre 2011 à 23:12 +0100, Samuel Thibault a écrit :
>> >> Adam Borowski, le Sat 12 Nov 2011 23:08:08 +0100, a écrit :
>> >>> You need
Ole Wolf writes:
> I have a problem building a package properly. From a clean build, sources-only
> (debuild clean; debuild -S), I get the lintian warning that the
> diff-contains-substvars in one of the packages that are built:
>
> W: vellemaninstrumentation source: diff-contains-substvars debia
Niels Thykier writes:
> On 2011-11-05 21:22, Niels Thykier wrote:
>>
>> Hi,
>>
>> I would like to propose the goal of getting archive-wide support for
>> the optional debian/rules targets "build-arch" and "build-indep".
>> The intention is to finally solve issues like #619284 and the goal
>> is
Daniel Ruoso writes:
> I have been thinking about the bootstrapping of pakages lately. I am
> involved in bootstrapping a partial system -- no kernel and no libc --
> for some architectures for internal use. And I just thought that we
> could use one trick to help in the bootstrap of packages tha
Neil Williams writes:
> We've a few native packages which handle data in package-specific
> directories under /var/lib/. It would be convenient to specify the name
> of this directory in debian/rules as a -D define to the compiler
> (because it's native) and then pass that into the relevant maint
Joerg Jaspert writes:
> I just merged a patch from Ansgar to generate the Packages files without
> the English description embedded inside them. Instead they are now
> written into a new file, the "English Translation" file in
> "main/i18n/Translation-en.bz2". They thus appear alongside all other
Yaroslav Halchenko writes:
> Thank you John for extending my argument with adequate references which
> I have swallowed while composing my question email.
>
> And if we are after reading FHS /usr/lib section:
>
> /usr/lib includes object files, libraries, and internal binaries that
> are
Russ Allbery writes:
> Adam Borowski writes:
>
>> If they use AM_MAINTAINER_MODE and it's "disabled" [1], there's no way
>> to check if they aren't in DFSG and/or GPL violation by shipping
>> sourceless code. Forbidding it would at least deal with patching
>> autotools output rather than source
Paul Wise writes:
> On Wed, Jul 6, 2011 at 10:11 AM, Hamish Moffatt wrote:
>
>> Thanks all for the replies. I checked out apt-zip, apt-offline, aptoncd,
>> CDD and apt-clone. None of them really suited my needs, as I want to
>> generate this repository automatically, and want to do a whole class
Steve Langasek writes:
> On Wed, Jun 29, 2011 at 09:53:26AM +0200, Joachim Breitner wrote:
>> But for now, the resume is that we put it into the sysadminâs hand to
>> install nss packages for all architectures he thinks his users want to
>> run binaries on?
>
> Yes, that's the only option I see
Svante Signell writes:
> Hi,
>
> Tried to google but did not find any useful so far. I have a package I'm
> porting, and want to create one out of two binary packages from the
> source. Is there an easy way to achieve this, e.g. by an override
> statement. Or is brute force, removing all entries
Scott Kitterman writes:
> If 3.0 (quilt) didn't apply patches by default I'd have no reason not to just
> use it. Keeping local_options in a VCS is a bit of a workaround for this,
> but
> it seems wrong to have a persistent diff between what's in the VCS for a
> package and what's in the arc
Stefano Rivera writes:
> Hi Scott (2011.06.02_16:30:13_+0200)
>> Keeping local_options in a VCS is a bit of a workaround for this
> ...
>> I'd really like to have a way to just control this globally on my system.
>
> +1 to that. Esp for team-maintained packages where people have different
> prefe
Charles Plessy writes:
> Le Thu, Jun 02, 2011 at 11:11:30AM +0200, Goswin von Brederlow a écrit :
>>
>> apt-get source foo
>> work on package
>> debuild
>> test
>> # Optionally: Just to be nice and fill out the header
>> # This would be impro
Guido Günther writes:
> On Thu, Jun 02, 2011 at 11:11:30AM +0200, Goswin von Brederlow wrote:
>> Scott Kitterman writes:
>>
>> > On Wednesday, June 01, 2011 10:26:59 AM sean finney wrote:
>> >> On Wed, Jun 01, 2011 at 02:39:42PM +0200, Goswin von Brede
Scott Kitterman writes:
> On Wednesday, June 01, 2011 10:26:59 AM sean finney wrote:
>> On Wed, Jun 01, 2011 at 02:39:42PM +0200, Goswin von Brederlow wrote:
>> > And note that as maintainer or for the VCS copy you can allways
>> > configure debian/soruce/local-option
"Bernhard R. Link" writes:
> * Scott Kitterman [110531 14:36]:
>> For some of us (me anyway), applying patches when unpacking a
>> source package is just the wrong kind of automagic. I'd like to
>> have patches applied when I say they should be applied.
>
> Please think of the children^H^H^H^H^H
Joachim Breitner writes:
> Hi,
>
> Am Dienstag, den 31.05.2011, 09:18 +0200 schrieb Goswin von Brederlow:
>> Joachim Breitner writes:
>> > BTW, for all who create patches this way and want to later split the
>> > patch into two logically independent patches,
Joachim Breitner writes:
> Hi,
>
> Am Sonntag, den 29.05.2011, 11:26 +0200 schrieb Josselin Mouette:
>> > But it still happens that those patches are generated[1] when the
>> > maintainer
>> > did not expect any change at all. That's why we added the option
>> > --abort-on-upstream-changes for
Raphael Hertzog writes:
> Hello,
>
> from time to time I hear some rumblings about how "3.0 (quilt)" mixes
> badly with VCS. Indeed, one of the primary goals of the format
> was to not require prior knowledge of the patch system to be able to
> modify a package. And it's the case since you can do
Cyril Brulebois writes:
> Hi,
>
> Raphael Hertzog (29/05/2011):
>> from time to time I hear some rumblings about how "3.0 (quilt)"
>> mixes badly with VCS. Indeed, one of the primary goals of the format
>> was to not require prior knowledge of the patch system to be able to
>> modify a package.
Michael Banck writes:
> On Thu, May 26, 2011 at 02:20:48PM -0700, Steve Langasek wrote:
>> On Thu, May 26, 2011 at 04:52:38PM -0400, Mackenzie Morgan wrote:
>> > On Thu, May 26, 2011 at 4:49 PM, Benjamin Drung wrote:
>> > > Recommends or Suggests:
>> > > cdbs
>> > > cmake
>>
>> > My reasoning o
Fernando Lemos writes:
> On Thu, May 26, 2011 at 9:21 AM, Patrick Strasser
> wrote:
> [...]
>> Why not use some simple non-HTTP-protocol on port 80?
>
> That tends to break transparent proxying. If port 80 is the only one
> you have open, chances are you're behind a transparent proxy as well.
>
Ian Jackson writes:
> Goswin von Brederlow writes ("Re: Getting good bug reports"):
>> Ian Jackson writes:
>> > The reason why there is a problem with an http submission interface is
>> > that suddenly every idiot will think "oh I must write a c
Ian Jackson writes:
> Goswin von Brederlow writes ("Re: Getting good bug reports"):
>> So everyone is allowed to write a frontend to report bugs via smtp. But
>> only reportbug is allowed to use http? That seems a bit stupid.
>
> No-one _wants_ to write a fronte
Ian Jackson writes:
> Brian May writes ("Re: Getting good bug reports"):
>> [ explanation of how reportbug is broken right now ]
>
> We could solve this if we can avoid the slippery slope problem.
>
> Or to put it another way, I would have no objection to an http
> submission interface to the BTS
jida...@jidanni.org writes:
> Say, for the sake of sharing a single .deb offline, what bad thing might
> happen if I run the -486 kernel on my other machines where I could run
> the -pae kernel? Namely other single Celerons having the pae capability.
Nothing happens. You just won't be able to use
jida...@jidanni.org writes:
>> "RC" == Russell Coker writes:
> RC> Why not just install the other kernel and try booting it?
> Maybe it will lead to subtle data loss. You never know. That's why I was
> hoping to dig out of the .debs just how they determine which Thinkpads
> are hip, and which
David Kalnischkies writes:
> environment. I can already hear someone asking for
> Package: libc6
> Recommends: libc6-686 {arch::supports:cmov}
> which soon evolves to a complete language in which you really need
> all the funky stuff like & and | and ! together with hard/soft constraints
That c
Pedro Larroy writes:
> Hi
>
> I think expecting having a working smtp on laptops, workstations, etc,
> is unreasonable these days.
And you don't. See docs or other mails.
> I suggest that we can make an HTTP based bug reporting method.
The only advantage of this would be for systems that firew
peter green writes:
> (note: this message quotes from multiple mails by different people)
>
> Wouter>First and foremost, I do not believe that setting -Werror in a
> Wouter>debian/rules file is the best way to maintain a package; -Werror is a
> Wouter>development option which should not be used i
"Eugene V. Lyubimkin" writes:
>> > > and secondly, this is easily abusable by third-package maintainers
>> > > and even packages from completely different, non-Debian
>> > > repositories:
>> > >
>> > > Package: some-package
>> > > Depends: gnome
>> > > Recommended-When: gnome
>>
>> Third-party r
"Eugene V. Lyubimkin" writes:
> On 2011-05-21 21:41, Ian Jackson wrote:
>> Simpler than this, and simpler than constructions involving negations
>> (which would be very troublesome for the resolution algorithms), would
>> be:
>>
>> Package: A-plugin-B
>> Depends: A, B
>> Recommended-When:
Marc Haber writes:
> On Sun, 22 May 2011 00:29:35 +0200, Goswin von Brederlow
> wrote:
>>(c) Modify ifupdown to notice when additional IP addresses come up (or
>>go away) and run the ifup.d (ifdown.d) scripts for it.
>
> One would need an ifupdownd for this. I don&
Marc Haber writes:
> Hi,
>
> with the increasing deployment of IPv6 I begin to see an issue
> icreasingly often: When an interface is configured for IPv6, it takes
> a few seconds before the IPv6 address actually becomes available.
> Services that are started in this time window won't listen on I
Didier Raboud writes:
> Wouter Verhelst wrote:
>
>> I was working on nbd-server upstream, and so had ran ./configure with
>> CFLAGS='-Wall -Werror', which I consider good practice when writing C
>> code.
>>
>> What I didn't notice immediately was that gcc was emitting some
>> warnings, but that
Roger Leigh writes:
> On Thu, May 12, 2011 at 06:31:48PM +0200, Goswin von Brederlow wrote:
>> Adam Borowski writes:
>> >> Should we try to make this work (at best badly) since a change in
>> >> mount options in /etc/fstab would only take effect at the next
>
Adam Borowski writes:
> On Sat, May 07, 2011 at 10:43:29PM -0400, Ted Ts'o wrote:
>> This isn't a bug in e2fsprogs; e2fsprogs has absolutely nothing to do
>> with mounting the file system.
>>
>> Debian simply doesn't support the mount options for the root file
>> system in /etc/fstab having any
David Paleino writes:
> Hello everybody,
> I'm writing this mail to gather comments about a serious bug I received some
> time ago, for which I haven't yet had time to make a proper fix. The bug is
> #612918, against wicd, "Uses /etc/wicd/wireless-settings.conf as state file".
>
> My opinion is t
Pierre Habouzit writes:
> On Thu, May 05, 2011 at 06:51:35PM +0200, Goswin von Brederlow wrote:
>> Pierre Habouzit writes:
>>
>> > On Wed, May 04, 2011 at 10:19:45PM +0200, Josselin Mouette wrote:
>> >> Le mercredi 04 mai 2011 ÃÂ 22:12 +0200, Lucas Nussbau
Pierre Habouzit writes:
> On Wed, May 04, 2011 at 10:19:45PM +0200, Josselin Mouette wrote:
>> Le mercredi 04 mai 2011 à 22:12 +0200, Lucas Nussbaum a écrit :
>> > While I like the idea in general, I think that it should also be
>> > possible to upload packages directly to rolling (through
>>
Josselin Mouette writes:
> This way, when something is broken in testing and cannot be unbroken
> quickly, a maintainer who notices it could add (or make the people in
> charge add) the necessary packages to the override file. If, for a
> reason or another, an important bug fix or a security upda
301 - 400 of 2310 matches
Mail list logo
