contradict explicitly on the
> > version numbering of an NMU of a native package.
>
> The developer's reference chose to ignore or change a longstanding practice
> of never using debian revision numbers in native packages. Changing this
> breaks software that has relied on
>
> My inclination would be decline requests to add unrelated packages to
> psutils, but I thought I'd solicit input from others in case someone
> has some perl (oops, pearl) of wisdom that I have overlooked. Thanks!
Maybe you could consider to add a package psutils-addons or some
r", "package libbar1",
> or "package libbar-dev". I think this functionality would have to be
> implemented on the BTS side.
It could however say package bar,libbar1,libbar-dev and any package from
the list will do :-)
Cheers
Luk
-BEGIN PGP SIGNATURE-
Version
identifier is reported only once
thotswap.c:187: error: for each function it appears in.)
make[2]: *** [thotswap.o] Error 1
make[2]: Leaving directory `/home/luk/tmp/toshutils-2.0.1/src'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/luk/tmp/toshutils-2.0.1'
make: *** [b
sign the
> current yorick-1.5.14-1 package.)
you might want to have a look at [1] as that is the procedure to follow
to have a new key added to the keyring when you don't have any existing
valid key anymore AFAICT.
> Thank you very much for any help you can provide; I apologize for
>
pond to my intention to NMU...
> You could of course disagree about whether it's a bug or not, but in that
> case, you would want to appeal to the tech-ctte, not debian-devel.
...before going to the Technical Committee.
Cheers
Luk
--
Luk Claes - http://people.debian.org/~luk - GPG k
Anthony Towns wrote:
> On Thu, Jan 12, 2006 at 06:48:38PM +0100, Luk Claes wrote:
>
>>>But if you read this bug (#307833), you'd see that the maintainer doesn't
>>>consider it a bug, and has documented why in the README file.
>>
>>It is a bug as
> problems related to game development and games packages in Debian. You can
> join that list at:
[...]
> You're welcome to join the group, or say whatever you think about this
> project.
I think it's a marvellous idea as gaming is one of the aspects that is
IMHO still
wget.
The current intent to NMU is proposing curl | wget which doesn't need
any modification to the config file if curl is installed. Though you're
right that you still need to change the config file when curl is not
installed. This is IMHO however not a *severe* bug as some packages need
conf
s this just a bug in the qa scripts, or worse?
It's just a matter of britney not been running the last couple of days
AFAIK (though it has run today... so it will probably be shown as 1 days
old tomorrow?).
Cheers
Luk
--
Luk Claes - http://people.debian.org/~luk - GPG key 1024D/9B7C328D
Fi
Frank Küster wrote:
> Luk Claes <[EMAIL PROTECTED]> wrote:
>
>
>>Frank Küster wrote:
>>>http://qa.debian.org/developer.php?excuse=tetex-base
>>>
>>>says that tetex-base is 0 days old. However, unstable has 3.0-13 which
>>>was uploaded
an register a
keysigning request on [1] (which looks very similar as [0] indeed).
I'll also contact the remaining DDs in the neighbourhood and ask them to
contact you.
Cheers
Luk
[1] http://nm.debian.org/gpg.php
PS: The contact address for keysigning coordination is
[EMAIL PROTECTED] as list
e upstream package and I dont want to remove it or
>>rename it.
>>
>>
>
> rename /usr/bin/git to /usr/bin/cogito-git or whatever. It is not that hard.
Or why not usr/bin/cogit or usr/bin/git-common or something like that?
Cheers
Luk
-BEGIN PGP SIGNATURE-
Version:
tures where the package is not built
anymore which is the other solution to get these kind of packages into testing.
Cheers
Luk
--
Luk Claes - http://people.debian.org/~luk - GPG key 1024D/9B7C328D
Fingerprint: D5AF 25FB 316B 53BB 08E7 F999 E544 DE07 9B7C 328D
signature.asc
Description:
in main, I put it above NOTA.
Cheers
Luk
--
Luk Claes - http://people.debian.org/~luk - GPG key 1024D/9B7C328D
Fingerprint: D5AF 25FB 316B 53BB 08E7 F999 E544 DE07 9B7C 328D
signature.asc
Description: OpenPGP digital signature
host and
wanna-build [1] [2] [3].
Don't hesitate to add or improve content of the page, it's a wiki page after
all...
Cheers
Luk
[0] http://wiki.debian.org/Buildd/BuildLogs
[1] http://kmuto.jp/open.cgi?buildd
[2] http://www.debian.org/devel/buildd/
[3] https://db.farm.ftbfs.de
the RFC differ from the authentic RFC
>6 FETCH-FAIL
Note that not all authentic RFC documents have the same license, some of them
are probably even DFSG compliant...
So there can be more than 79 false positives...
Cheers
Luk
--
Luk Claes - http://people.debian.org/~luk - GPG key 102
Manoj Srivastava wrote:
> Hi,
Hi Manoj
Can everyone please focus on the release and discuss things that don't help to
release on December 4th at all till after that date?
Thank you very much.
Luk
PS: For those people that seem to think they can't help: there is still a long
li
Manoj Srivastava wrote:
> Dear Luk,
>
> On Wed, 25 Oct 2006 08:16:59 +0200, Luk Claes <[EMAIL PROTECTED]> said:
>
>> Manoj Srivastava wrote:
>>> Hi,
>
>> Hi Manoj
>
>> Can everyone please focus on the release and discuss things that
>>
Joerg Jaspert wrote:
> On 10818 March 1977, Luk Claes wrote:
>
>> Can everyone please focus on the release and discuss things that don't help
>> to
>> release on December 4th at all till after that date?
>
> No, the release is no reason to stop everything els
Manoj Srivastava wrote:
> On Wed, 25 Oct 2006 18:51:26 +0200, Luk Claes <[EMAIL PROTECTED]> said:
>
>> Joerg Jaspert wrote:
>>> On 10818 March 1977, Luk Claes wrote:
>>>
>>>> Can everyone please focus on the release and discuss things that
>&g
tp-master.d.o AFAIK.
Cheers
Luk
--
Luk Claes - http://people.debian.org/~luk - GPG key 1024D/9B7C328D
Fingerprint: D5AF 25FB 316B 53BB 08E7 F999 E544 DE07 9B7C 328D
signature.asc
Description: OpenPGP digital signature
he
first place or did he not ask for it...
Cheers
Luk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
inst inform?
important
Cheers
Luk
--
Luk Claes - http://people.debian.org/~luk - GPG key 1024D/9B7C328D
Fingerprint: D5AF 25FB 316B 53BB 08E7 F999 E544 DE07 9B7C 328D
signature.asc
Description: OpenPGP digital signature
blems you think will not be
solved on time?
Cheers
Luk
PS: Please, don't send this kind of messages if you can't elaborate or
at least put a smily behind it so we know you don't really mean it :-)
--
Luk Claes - http://people.debian.org/~luk - GPG key 1024D/9B7C328D
Fingerpri
ss old data.
>
>
> You might want to check https://www.biglumber.com/ which contains
> already a very nice interface for all of this.
Or you might want to use https://nm.debian.org/gpg_offer.php. Have a
look at https://nm.debian.org/gpg.php if you want to be listed...
Cheers
Luk
--
Luk Claes - http://people.debian.org/~luk - GPG key 1024D/9B7C328D
Fingerprint: D5AF 25FB 316B 53BB 08E7 F999 E544 DE07 9B7C 328D
signature.asc
Description: OpenPGP digital signature
g and in the
uid of your key... If the "John Doe <[EMAIL PROTECTED]>" doesn't
match 100% you'll get the above failure...
>>From man dpkg-buildpackage:
>
>-kkey-id
> Specify a key-ID to use when signing packages.
This is only needed when
ally build the packages more than once before
> uploading as I often find some last-minute bug, and don't like to
> type in my gpg-passphrase more frequently than necessary.
Even than you should not need to specify the -kkeyid...
Cheers
Luk
- --
Luk Claes - http://people.debian
Package: wnpp
Severity: wishlist
Owner: Luk Claes <[EMAIL PROTECTED]>
* Package name: libcrypt-openssl-bignum-perl
Version : 0.03
Upstream Author : Ian Robertson <[EMAIL PROTECTED]>
* URL : http://cpan.org/
* License : same as Perl
Programmin
Package: wnpp
Severity: wishlist
Owner: Luk Claes <[EMAIL PROTECTED]>
* Package name: libcrypt-openssl-rsa-perl
Version : 0.23
Upstream Author : Ian Robertson <[EMAIL PROTECTED]>
* URL : http://cpan.org/
* License : like Perl
Programmin
Package: wnpp
Severity: wishlist
Owner: Luk Claes <[EMAIL PROTECTED]>
* Package name: libcrypt-openssl-dsa-perl
Version : 0.13
Upstream Author : T.J. Mather, E <[EMAIL PROTECTED]>
* URL : http://cpan.org/
* License : like Perl
Programmin
Package: wnpp
Severity: wishlist
Owner: Luk Claes <[EMAIL PROTECTED]>
* Package name: libcrypt-openssl-random-perl
Version : 0.03
Upstream Author : Ian Roberts <[EMAIL PROTECTED]>
* URL : http://cpan.org/
* License : like Perl
Programmin
ally taken care of near a
release because of the transitioning problems... If the meta packages
get to testing earlier it's very probable they will not be installable
for a long time...
Cheers
Luk
--
Luk Claes - http://people.debian.org/~luk - GPG key 1024D/9B7C328D
Fingerprint: D5AF 25FB 316B
uploaded to the
(not zero days) delayed queue or when the package enters the NEW queue.
Because of this some people might prefer to send the patches to existing
bugs when NMUing even if there are many bugs involved...
To summarize: I would like the patch to be applied and I propose to not
change
; for a general solution and not one that only applies to asis.
This is already known by the Release Team, I'm not sure if the news has
already reached the P-a-s maintainers...
> PS. Please reply to me directly, as well as to the list.
Ok.
Cheers
Luk
[1] These maintainers are list
her unless they will
still be installable in testing and the version in unstable is not ready
to enter testing yet (not old enough, RC bug, not built on all release
arches...)
To conclude, please try to avoid linking transitions together and try to
avoid making packages instantly uninstallable i
Miles Bader wrote:
> [EMAIL PROTECTED] (Marco d'Itri) writes:
>
>>>I presume that default kernels need legacy ptys to support older systems
>>>that don't use udev, right?
>>
>>Wrong. Nothing needs BSD ptys but some *very* old applications (I would
>>not even know where to find one).
>
>
> I was
hough it takes into account
any follow-up on the bug report to reset the timer which you clearly
don't...
> click this to get a quick overview: :-D
> http://debian.binera.de/wnpp/?type%5B%5D=ITA&type%5B%5D=ITP&sort=age;desc
Cheers
Luk
--
To UNSUBSCRIBE, email to [EMAIL PRO
I ask
> for xmms-xf86audio removal now, or wait?
xmms removal was decided some time ago.
Yes, if the package is useless without xmms and cannot be adapted to one
of xmms' alternatives, you should ask for removal of your package.
Cheers
Luk
--
To UNSUBSCRIBE, email to [EMAIL PROTE
Sebastian Pipping wrote:
> Luk Claes wrote:
>> xmms removal was decided some time ago.
>
> i am working on a project partly depending
> on parts of xmms. in case it is removed
> i will need at least backups of all
> related package sources so i can still
> have the pack
o?
>
> I uploaded the package again last night but it similarly disappeared.
>
> [0] http://people.debian.org/~edmonds/ip4r/
It was rejected with the following message:
Rejected: ip4r_1.03-1_multi.changes: Missing mandatory field `description'.
You should have got a REJE
ke you said, it's production, so there is no need to upgrade at all...
Any decent argument left?
Cheers
Luk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ment unless necessary for new features AFAICT, so for someone who
is used to backport it should still be straight forward either way AFAICS.
Cheers
Luk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
;t have the core packaging
> software maintained by an obstructive and naive programmer supported
> by someone who is more interested in pretty revision logs than good
> code.
Confrontation is not going to solve this dispute in your advantage, on
the contrary...
Cheers
Luk
--
To UNSUBSCRIBE
r is there anything I could
> do myself about this?
Hmm, you do realise that lcd4linux is mentioned in P-a-s because it
includes sys/io.h, right? So this is not similar at all...
Cheers
Luk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Andreas Tille wrote:
> On Wed, 19 Mar 2008, Charles Plessy wrote:
>
>> By the way, is there a way to install package with all the 'Suggest'ed
>> dependancies, something like aptitude install bioperl --with-suggested
>> ? I have
>> not found anything in the manpage.
>
> Neither did I in man apt-ge
Andreas Tille wrote:
> On Wed, 19 Mar 2008, LUK ShunTim wrote:
>
>> "man apt.conf" points you to
>> /usr/share/doc/apt/examples/configure-index.gz. Maybe it has something
>> you want. :-)
>
> Ahhh, nice place to hide some information. Users only have
which means this is a security upload
>> Or any other stable upload, yes?
>
> Yes, sorry. I forgot that those exist as well. :-)
Why are we bothering to make something up if everyone is using etch etc?
Cheers
Luk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: wnpp
Severity: normal
I request assistance with maintaining the bash-completion package.
Upstream has handed over the maintenance, so working on the package is
also working on upstream...
I've set up an alioth project to coordinate, but the import of the
history and current state still n
Package: wnpp
Severity: normal
I request assistance with maintaining the update-inetd package.
I've quite recently taken over the maintainership of update-inetd. Any
help on bug triage and/or co-maintainership would be welcomed.
The package description is:
This package provides a program used b
bian services (yet?).
Cheers
Luk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Peter Jordan wrote:
> Luk Claes, 04/07/08 20:05:
>
>> Peter Jordan wrote:
>>> Hi,
>> Hi
>>
>>> why are the keyrings of debian-multimedia.org and debian backports not
>>> in the official repository of debian?
>>>
>>> At
Ron Johnson wrote:
> On 04/07/08 13:20, Luk Claes wrote:
>> Peter Jordan wrote:
>>> Luk Claes, 04/07/08 20:05:
>>>
>>>> Peter Jordan wrote:
>>>>> Hi,
>>>> Hi
>>>>
>>>>> why are the keyrings of debian-multi
> response to the patch have just been ignored.
According to the bug log the patch was not ready when the maintainer
wanted to apply it and nobody bothered to start an NMU process...
Cheers
Luk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Goswin von Brederlow wrote:
> Luk Claes <[EMAIL PROTECTED]> writes:
>
>> Goswin von Brederlow wrote:
>>> Ove Kaaven <[EMAIL PROTECTED]> writes:
>>>> The way I understand it, they HAVE been pushing... and pushing... for
>>>> a long
oublesome signing is done in a
production/desktop environment (oldstable/stable/whatever).
Cheers
Luk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
or policy for such hard-to-reach Developers with
> regard to hi-jacking or NMU?
There is a guideline for doing NMUs which kind of includes this case in
the Developer's Reference...
Cheers
Luk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ut back a service I've disabled. (Sure this
> won't be needed with dependency based boot system, but in the meantime
> it still is.)
Isn't this just a matter of stopping the service and renaming the S (K)
links to s (k) links so one can easily revert?
Cheers
Luk
--
To UNSUBSCRIBE
e RC bug "Should not enter testing" and forget about
> the problem with clive in stable releases forever?
I guess the question is rather debian-volatile or backports.org and
maybe it would be better to use volatile-sloppy?
Cheers
Luk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTE
t;
> If main text is s/RSA/RSA\/DSA/g , I understand script example but ...
>
> Is there any reason to use DSA key insted of RSA key(~/.ssh/id_rsa.pub) ?
On the contrary, it's better to use RSA keys as they can be bigger and
are faster.
Cheers
Luk
--
To UNSUBSCRIBE, email to
mips mipsel powerpc sparc)
> edenmath.app
> gnome-chemistry-utils
> virt-manager
> gsynaptics
> ucspi-proxy
> epiphany-extensions
What does this list mean?
> Should be in in P-a-s (or not-for-us?)
> --
Did you contact P-a-s administrators (and buildd maintainers) about it?
Cheers
Luk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
sync everything unless explicitely stated differently and will keep
working without intervention for the time being? Because otherwise it's
like Joerg said not an option IMHO.
Cheers
Luk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Raphael Geissert wrote:
> Luk Claes wrote:
>> Are you sure that the current sync scripts make that possible and won't
>> sync everything unless explicitely stated differently and will keep
>> working without intervention for the time being? Because otherwise it's
&
nce in the list you get from rc-alert might prevent your
apparently changing view...
> Artificially lowering the RC count in Testing is not always
> preferential to keeping Testing in a state amenable to testing.
You say yourself that it's not artificially as RC bugs in "n
Robert Edmonds wrote:
> On 2008-06-13, Henrique de Moraes Holschuh <[EMAIL PROTECTED]> wrote:
>> On Fri, 13 Jun 2008, Martín Ferrari wrote:
> rarp is obsolete.
It's not, I do use it from time to time, do you have a replacement?
Cheers
Luk
--
To UNSUBSCRIBE, email to [
m is the only way to get a trusted path to the bpo
> repository is by fetching debian-backports-keyring from it, checking your
> signature in its .dsc, etc. So this is what I'm trying to solve.
Hmm, are there not 2 other ways documented on backports.org as you can
see below?
Cheers
Lu
for comments
> and [EMAIL PROTECTED] as they'd have to do it.
>
> I'd like to also note that dpkg conflicts with the old version of
> apt/aptitude, so this will also force the upgrade of apt/aptitude.
Requiring from everyone wanting to upgrade to first manually upg
sign that we already lost against spammers?
Cheers
Luk
Original Message
Subject: Delivery Status Notification (Failure)
Date: 30 Jun 2009 23:05:42 +0200
From: Mail Delivery System
To: l...@debian.org
The following message to was undeliverable.
The reason for the problem:
an extra source of errors.
It should also only affect external scripts that are bash specific
AFAICS and they would be easily 'fixed' by changing bin/sh to bin/bash
in the shebang (can even happen unconditionally).
Cheers
Luk
--
To UNSUBSCRIBE, email to debian-devel-requ...@li
g issues solved soon after it would be forced in.
Cheers
Luk
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
maximilian attems wrote:
> On Sat, Jul 11, 2009 at 01:08:05PM +0200, Luk Claes wrote:
>> It needs quite some work to get reverse dependencies handled and getting
>> it built on all architectures. Both of which are the main responsability
>> of the kernel team...
>
> it
hem on merkel:/srv/ftp.debian.org/queue/reject/*.reason
Cheers
Luk
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
er of retitling the ITA
bug to RFA again.
Cheers
Luk
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
... Please do note that I'm talking about errors, not about
warnings.
Cheers
Luk
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Wouter Verhelst wrote:
On Fri, Jul 17, 2009 at 11:44:54AM +0200, Luk Claes wrote:
Wouter Verhelst wrote:
On Fri, Jul 17, 2009 at 11:19:50AM +0200, Steffen Moeller wrote:
Not? Was the originally uploaded package correct? Amazing. Hm. Then,
it should be lintian errors that denote a build as a
Wouter Verhelst wrote:
On Fri, Jul 17, 2009 at 12:10:56PM +0200, Luk Claes wrote:
Wouter Verhelst wrote:
Right. However, having sbuild run lintian would allow a buildd
maintainer to assess issues with packages by looking at *warnings*,
rather than 'just' errors. This isn'
u're letting people install it now, so on
first _install_ it's going to divert it without prompt? Or is
that part of the "interactive upgrade"?
No, on first installation it will ask.
Cheers
Luk
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a
quite some bashisms around...
Cheers
Luk
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
now and we did not want to bother people
during d-i or debootstrap and having bash depend on dash made that easier.
Cheers
Luk
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
proposal.
However, I think I and a lot of other people would appreciate clarity,
so far not expressed, about why dash needs to be essential.
You do not want to give the possibility to remove /bin/sh from the
system. Currently this is done by making the default system shell essential.
Cheers
Luk
y to avoid depending on bash features. Currently the one in shadow is
already being taken care of and the one in libpam0g is being considered.
Cheers
Luk
PS: Please be a bit more positive, we now that things are moving slowly,
but at least they are moving.
--
To UNSUBSCRIBE, email to de
Manoj Srivastava wrote:
On Sun, Jul 26 2009, Luk Claes wrote:
Goswin von Brederlow wrote:
A faster and smaller default system shell is important to a lot of our
users.
I see this asserted a lot. I am pretty sure that the average
user very likely does not care. The embedded system
Jonathan Wiltshire wrote:
On Sun, Jul 26, 2009 at 05:08:20PM +0200, Luk Claes wrote:
On upgrades you are asked if you want to have dash as default system
shell unless you have dash already installed, then we leave it as
is.
On my unstable box I received dash a few days ago, because an upload
tion that works in a more flexible way is far
from trivial and it does not seem like anyone is interested enough to
work on it.
Cheers
Luk
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
ts it is being updated from a system that has bash as
/bin/sh. Didn't see a plan for that. If that is planed then be a step
forward.
It's what has been implemented.
Cheers
Luk
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe&quo
Goswin von Brederlow wrote:
Luk Claes writes:
Manoj Srivastava wrote:
On Sun, Jul 26 2009, Luk Claes wrote:
Goswin von Brederlow wrote:
A faster and smaller default system shell is important to a lot of our
users.
I see this asserted a lot. I am pretty sure that the average
user
specific CPUs or similar.
> Will there be a Build-Arch field or a way to override discarding
> uploaded .debs?
There will be a Build-Arch field or some other way to make sure the
arch:all packages can be built reliably.
Cheers
Luk
--
To UNSUBSCRIBE, email to debian-devel-requ
386.
This will be solved by an extra field which tells on what arch the
arch:all package should be built (or a similar solution to the same effect).
Cheers
Luk
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
e specific reasons why the maintainer seems to
be inactive.
Also note that there is a process for tracking possible orphaning or
removal of a package by the QA Team which is called bapase [1].
Cheers
Luk
[1] http://wiki.debian.org/qa.debian.org/bapase
--
To UNSUBSCRIBE, email to debian-dev
line: 6-8 months (can be done in tandem with a, if here were
> more people working on it)
Are the issues identified already or do you have an idea about how many
issues there are to tackle?
Do you have any documentation for possible contributors to help you with
this?
Cheers
Luk
--
To UNS
ve is perfectly okay, after having
> considered those downsides. That's pretty much what I was saying in my
> previous mail.
Yes, though only after considering all the downsides, including having
these discussions and people requesting you to reconsider from time to time.
Cheers
Luk
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
ly a shame to see
> weeks of work going down the drain due to political restrictions.
Hmm, nothing is black and white. The current way of uploading
clamav-data is suboptimal and ftpmasters don't want that to continue
when volatile is integrated in the main archive. Though that does no
bly better spent by
talking to ftpmas...@d.o and implementing a solution btw.
Cheers
Luk
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
e issues so 2.6 can at least be in Squeeze, but
> apparently this list does not exist.
AFAIK the process of filing and fixing bugs to be able to build with
python 2.6 is already happening.
Cheers
Luk
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
1] and
file bugs where necessary (please don't file duplicates nor file bugs
when fixing the build chroot or setting a dep-wait would suffice).
Cheers
Luk
[1] https://buildd.debian.org/status (click on the architecture you are
interested in and look at the Failed, Build-Attempted and M
ny packages not conforming. So either policy is
wrong there or policy is normative which would mean that there are a lof
of other bugs in policy that noone cares about fixing (or even filing).
Cheers
Luk
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of &
" severity. We should not be
> blocking packages from the archive for such low-severity issues; please drop
> this check.
It would indeed be good to have consensus first on the severity and
certainty of a lintian check before auto rejecting on it IMHO.
Cheers
Luk
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
they fit
the way he can use them at the moment he needs them. As long as that
continues I'm not going to even try to get the Debian Policy and RC bug
policy consistent and the Debian Policy will remain not useful for
anything release related as it will be incomplete and sometimes
conflicting wit
Russ Allbery wrote:
> Luk Claes writes:
>
>> As before Manoj seems to interpret things and word things so they fit
>> the way he can use them at the moment he needs them. As long as that
>> continues I'm not going to even try to get the Debian Policy and RC bug
Matthew Johnson wrote:
> On Mon Nov 02 11:40, Luk Claes wrote:
>> For the actual matter at hand I think it's very wrong to do a MBF
>> without going through d-devel for several reasons:
>
>>
>
> Otoh, this is a slightly special case, since they are things
1 - 100 of 312 matches
Mail list logo
