Mike Hommey <[EMAIL PROTECTED]> writes:
> On Sun, Mar 02, 2008 at 07:10:20PM -0800, Russ Allbery wrote:
>> Yeah, that's pathological enough that I don't see any easy fix for it
>> in lintian without special-casing the perl package or not doing
>> encoding checks on misnamed changelog files. The l
On Sun, Mar 02, 2008 at 07:10:20PM -0800, Russ Allbery wrote:
> Adam Borowski <[EMAIL PROTECTED]> writes:
>
> > The package "perl" doesn't ship its own copy of changelog.Debian, but
> > instead relies on it's dependency, perl-base. Yet, it does ship other
> > stuff in /usr/share/doc/perl/, includ
Discussion on the technical details of using dpkg-divert for configuration
seems to have died down. My basic summary of the discussion is (A) any
system attempting to configure site defaults requires use of dpkg-divert
on conffiles[1], and probably should use dpkg-divert on all configuration
f
Adam Borowski <[EMAIL PROTECTED]> writes:
> The package "perl" doesn't ship its own copy of changelog.Debian, but
> instead relies on it's dependency, perl-base. Yet, it does ship other
> stuff in /usr/share/doc/perl/, including the upstream changelog.
Oh, so lintian gets confused and thinks tha
On Sun, Mar 02, 2008 at 06:11:22PM -0800, Russ Allbery wrote:
> Bas Zoetekouw <[EMAIL PROTECTED]> writes:
>
> > Of those, perl is a false positive (caused by lintian not detecting the
> > correct changelog file),
>
> Please provide more details? I know perl does odd things (relative to
> most De
Bas Zoetekouw <[EMAIL PROTECTED]> writes:
> Of those, perl is a false positive (caused by lintian not detecting the
> correct changelog file),
Please provide more details? I know perl does odd things (relative to
most Debian packages) with the changelog file, but I don't know why that
would caus
Michael Casadevall <[EMAIL PROTECTED]> writes:
> What about simply decoupling mips/mipsel's version numbers so an out of
> date package on mips(el) doesn't stall out the rest of the
> testing. Having (somewhat) setup britney/update_out to generate testing
> for m68k, it should just be a matter of
Because they don't want to.
William
On Sun, 2008-03-02 at 17:30 -0500, Michael Casadevall wrote:
> What about simply decoupling mips/mipsel's version numbers so an out of
> date package on mips(el) doesn't stall out the rest of the testing. Having
> (somewhat) setup britney/update_out to genera
What about simply decoupling mips/mipsel's version numbers so an out of
date package on mips(el) doesn't stall out the rest of the testing. Having
(somewhat) setup britney/update_out to generate testing for m68k, it
should just be a matter of adding of adding mips and mipsels, to the
proper li
Hi Russ!
You wrote:
> Amaya <[EMAIL PROTECTED]> writes:
> > Bas Zoetekouw wrote:
>
> >> I'm planning to file bugs for packages that use non-UTF-8 encodings in
> >> debian/control and/or debian/copyright.
> >
> > Can you report on any progress in this?
>
> There are four source packages left wit
Amaya <[EMAIL PROTECTED]> writes:
> Bas Zoetekouw wrote:
>> I'm planning to file bugs for packages that use non-UTF-8 encodings in
>> debian/control and/or debian/copyright.
>
> Can you report on any progress in this?
There are four source packages left with changelog encoding problems:
http://l
* Luca Brivio <[EMAIL PROTECTED]> [2008-03-02 20:28]:
> Alle 19:48, sab 1 marzo 2008, Christian Perrier ha scritto:
> > If someone cares to listen: when you think about ITPing each and every
> > piece of FLOSS that pops around: think about *helping* people who
> > maintain existing packages instea
Amaya <[EMAIL PROTECTED]> writes:
> Important:
> lintian: Also check for not using invoke-rc.d in other scripts.
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=381485
I don't have a tremendous amount of free time to work on Debian right now
and what time I do have for lintian I'm putting into
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adam Dickmeiss (upstream) wrote:
> YAZ 3.0.24 is available. All source is now covered by 'Revised BSD' -
> including the CCL module. The ziffy part has been removed (is GPL). ziffy
> be distributed separately at a later time.
Thank you very much for
Bas Zoetekouw wrote:
> I'm planning to file bugs for packages that use non-UTF-8 encodings in
> debian/control and/or debian/copyright.
Can you report on any progress in this?
Is there a bug that already tracks this issue?
Thanks
--
·''`.Moi je voudrais bien, un beau matin, qu'il y ait
Alle 19:48, sab 1 marzo 2008, Christian Perrier ha scritto:
> If someone cares to listen: when you think about ITPing each and every
> piece of FLOSS that pops around: think about *helping* people who
> maintain existing packages instead of adding even more noise to our
> noisy bunch of various cra
Your message dated Sun, 2 Mar 2008 20:39:55 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Processed: Re: debmake is deprecated
has caused the Debian Bug report #469049,
regarding debmake is deprecated
to be marked as done.
This means that you claim that the problem has been dealt
My bad, all of these package are not found in stable or testing.
Transition is finished. Sorry for the noise.
Debian Bug Tracking System wrote:
> Processing commands for [EMAIL PROTECTED]:
>
> > owner 469049 Santiago Vila <[EMAIL PROTECTED]>
> Bug#469049: debmake is deprecated
> Owner recorded a
Processing commands for [EMAIL PROTECTED]:
> owner 469049 Santiago Vila <[EMAIL PROTECTED]>
Bug#469049: debmake is deprecated
Owner recorded as Santiago Vila <[EMAIL PROTECTED]>.
> # see below for explanation
> severity 372964 important
Bug#372964: xtranslate: debmake is deprecated
Severity set t
On 02/03/08 at 23:34 +0900, Charles Plessy wrote:
> I have not asked MIPS to be removed from the list of released
> architectures. I have asked testing migration to be uncoupled from MIPS
> building while the buildds are suffering. In a previous thread it has
> been suggested that this operation re
Package: general
Severity: normal
I am opening this bug to have a tracker for the "debmake is deprecated"
transition progress. See
http://lists.debian.org/debian-devel-announce/2006/03/msg00019.html for
details.
The remaining bugs, that will become blockers, tagged important, are:
#372973: cksfv
On Sun, Mar 02, 2008 at 11:49:30AM +0100, Marc 'HE' Brockschmidt wrote:
> Charles Plessy <[EMAIL PROTECTED]> writes:
> > For the moment, the answer is:
> > As a side effect trying to build ghc6 on MIPS, many (hundreds?) other
> > packages are blocked from migrating to testing for more than a m
Processing commands for [EMAIL PROTECTED]:
> unblock 438885 by 353660
Bug#353660: linda: Check for direct use of init.d, when invoke-rc.d should be
used instead
Bug#438885: Mass bug filing: must use invoke-rc.d
Was blocked by: 341413 341415 348259 348263 353660 367722 367725 367727 367729
367730
unblock 438885 by 353660
unblock 438885 by 367727
block 438885 by 381485
thanks
[18:21] >> amaya joins #debian-bugs
[18:42] < amaya> so what to do about
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=438885?
[18:43] < amaya> linda seems to be "dead" and jukebox-mercury is only present
in old
Package: wnpp
Severity: wishlist
Owner: Jan Hauke Rahm <[EMAIL PROTECTED]>
* Package name: squirrelmail-quicksave
Version : 2.4.2
Upstream Author : Paul Lesniewski <[EMAIL PROTECTED]>
* URL : http://www.squirrelmail.org/plugin_view.php?id=8
* License : GPL
Pro
Package: wnpp
Severity: wishlist
Owner: "Jaldhar H. Vyas" <[EMAIL PROTECTED]>
* Package name: libmodule-starter-perl
Version : 1.470
Upstream Author : Andy Lester <[EMAIL PROTECTED]>
* URL : http://search.cpan.org/dist/Module-Starter/
* License : GPL + Artistic
Le Sun, Mar 02, 2008 at 01:39:52PM +0200, Riku Voipio a écrit :
> If you want to positively influence the RM team to remove mips(el)
Dear all,
sorry for this extra email, but I do not want any misunderstanding.
I have not asked MIPS to be removed from the list of released
architectures. I have
On Sun, 02 Mar 2008, Mike Bird wrote:
> You've rattled on at great length without showing any value to git
> logs beyond providing clues to a successor developer where a
> predecessor falls under a bus part way through developing a feature.
That's still good enough for me. Seems that I got somethi
On Sun, 02 Mar 2008, Henrique de Moraes Holschuh wrote:
> On Sun, 02 Mar 2008, Robert Collins wrote:
> > Well, when I sat down some years back to do a couple of things with
> > dpkg; I found no need to consult change logs to understand the current
> > code of the time. Perhaps its quality has massi
On Sun, 02 Mar 2008, Robert Collins wrote:
> On Sun, 2008-03-02 at 02:09 -0300, Henrique de Moraes Holschuh wrote:
> > And I am completely *sure* it would not be irrelevant for me were I
> > debugging dpkg without a full, complete, dpkg-regular-developer level of
> > understanding of the code. Or
On 01/03/08 19:48 +0100, Christian Perrier wrote:
> There seems to be some crazyness about packaging new stuff these
> days. That would be fine.if only our existing packages were well
> maintained.which, for many of them is certainly not true.
Just for the record: every single package Rafa
Petter Reinholdtsen <[EMAIL PROTECTED]> wrote:
>> The buildd queues aren't FIFO, this has been explained already a
>> dozen times if not more.
>
> And every time that discussion surfaces, suggestions to include age in
> the formula used to calculate the build order are presented. Also
> suggestio
I see that my (inept but working) patches are not welcome right now. So,
I'll leave groff alone; just let me answer the issues raised.
On Sat, Mar 01, 2008 at 11:56:28PM +, Colin Watson wrote:
> On Fri, Feb 29, 2008 at 12:32:29AM +0100, Adam Borowski wrote:
> > On Thu, Feb 28, 2008 at 10:10:3
On Fri, Feb 29, 2008 at 08:22:51AM -0800, Mike Bird wrote:
> On Fri February 29 2008 06:29:07 Otavio Salvador wrote:
> > I personally apply this same policy on repositories that I work and it
> > usually makes much easier logs to read.
>
> I'm not a DD but I've been programming since 1963 when I w
On Sun, Mar 02, 2008 at 08:34:23PM +0900, Charles Plessy wrote:
> Thanks for the answer! Sometimes two letters are much clearer that
> longer sentences. I would have prefered that a good reason would be
> provided (do not tell me that you do not see an obvious difference
> between mips and mipsel w
On Sun, Mar 02, 2008 at 08:02:09PM +0900, Charles Plessy wrote:
> Le Sun, Mar 02, 2008 at 10:56:19AM +0100, Julien BLACHE a écrit :
> > In the MIPS case, the buildds are impacted by real technical problems
> > that take time and effort to get fixed.
> Exactly, and real technical problems mean real
Package: wnpp
Severity: wishlist
Owner: Roberto Lumbreras <[EMAIL PROTECTED]>
* Package name: geotrans
Version : 2.4.1
Upstream Author : National Geospatial Intelligence Agency <[EMAIL PROTECTED]>
* URL : http://earth-info.nga.mil/GandG/geotrans
* License : BSD
Le Sun, Mar 02, 2008 at 12:09:06PM +0100, Marc 'HE' Brockschmidt a écrit :
> Charles Plessy <[EMAIL PROTECTED]> writes:
> > Would it be possible to allow the migration in testing of the package
> > that are waiting for being build on mips or mipsel until the buildd
> > problem is fixed?
>
> Same a
On Sat, 2008-03-01 at 11:18 -0600, Manoj Srivastava wrote:
>
> Now, having bisecability could be useful (I have never used a
> bisect); I don't know what the effect of a version that does not
> compile or is otherwise buggy would have on the work flow.
Depending on the treatment of bra
Charles Plessy <[EMAIL PROTECTED]> writes:
> Would it be possible to allow the migration in testing of the package
> that are waiting for being build on mips or mipsel until the buildd
> problem is fixed?
Same answer as a few days ago: No.
Marc
--
Fachbegriffe der Informatik - Einfach erklärt
24
On Sun, 02 Mar 2008, Robert Collins wrote:
> On Sun, 2008-03-02 at 02:09 -0300, Henrique de Moraes Holschuh wrote:
>
>
> > And I am completely *sure* it would not be irrelevant for me were I
> > debugging dpkg without a full, complete, dpkg-regular-developer level of
> > understanding of the code
Le Sun, Mar 02, 2008 at 10:56:19AM +0100, Julien BLACHE a écrit :
> In the MIPS case, the buildds are impacted by real technical problems
> that take time and effort to get fixed.
Exactly, and real technical problems mean real nuisance.
Dear Release managers,
as you probably noticed, the mips b
Charles Plessy <[EMAIL PROTECTED]> writes:
> For the moment, the answer is:
>
> As a side effect trying to build ghc6 on MIPS, many (hundreds?) other
> packages are blocked from migrating to testing for more than a month.
Eh, what? You think that mips* is the problem here? What about the
missi
On Sun, 2008-03-02 at 02:09 -0300, Henrique de Moraes Holschuh wrote:
> And I am completely *sure* it would not be irrelevant for me were I
> debugging dpkg without a full, complete, dpkg-regular-developer level of
> understanding of the code. Or if I were trying to understand how dpkg
> works,
[Julien BLACHE]
>> Clearly, in the conflict of interest between the ghc6 MIPS users, and
>> the testing users on other arches, a choice has been made, of which I am
>> unhappy.
>
> No choice has been made. I don't know what you're on, but you'd better
> put it off.
The "I don't know what you're o
Charles Plessy <[EMAIL PROTECTED]> wrote:
>> He doesn't have to use unstable. He can use pinning for this specific
>> package.
>
> Sure, and he can also use dpkg -i. The question is: why should we ask
> him to make the effort?
He is using testing. We never made any commitment wrt availability in
On Sat, Mar 01, 2008 at 01:28:42PM +, Thiemo Seufer wrote:
> 2) The obvious solution is to add SATA disks to the buildds, this is
>currently in the works.
rem.rfc822.org done since 2008-02-22 - 120GB PATA Disk on a Promise UDMA
133 Controller.
> 1) Upgrades to 1-2 GB RAM are also currentl
On Sat March 1 2008 21:09:27 Henrique de Moraes Holschuh wrote:
> So, every change in dpkg code is *always* completely obvious, and you never
> need any extra information that is not in a comment?
>
> Really?
If some dpkg team members cannot be trusted to comment their code,
then they cannot be tr
48 matches
Mail list logo
