ets the metadata
of all of the other bugs to match the first one. I usually only try one
round of merge fixing before resorting to forcemerge for fiddly little
disagreements like this.
--
Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
if they're also frequently overridden.
(All of that being said, one of the problems with Lintian development
right now is that the test suite takes an excessively long time to run,
and it would be nice to improve that. I'm dubious that we can delete
enough tags and thus tests to make a huge difference, but it does help.)
--
Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
since it's been years
since I've worked on Lintian, but some of those MRs looked pretty obvious,
so I'm merging the ones where I'm reasonably sure that I won't break
anything. Someone can always revert if I make a mistake. :)
Axel, please let me know when (I wo
control messages until the software to issue
signatures with the old key is no longer supported.)
[1] https://www.eyrie.org/~eagle/usefor/other/pgpverify
I kept meaning to write an RFC but never got around to it.
--
Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
Paul Wise writes:
> On Fri, 2022-04-29 at 17:04 -0700, Russ Allbery wrote:
>> Yes, verifying signatures using obsolete keys or obsolete algorithms
>> which are no longer supported in GnuPG 2.
> and nothing other than GnuPG 1 supports these keys?
I'm personally not aware
2 keys: 84
gpg: unchanged: 17
(I'm not intending this to be an argument for keeping GnuPG 1.x. The
forcing factor of Debian dropping support for the old keys may even be
useful. But it may be helpful for judging the impact.)
--
Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
mantically "wrong" thing and suggest people
switch to using https even though that's not a "different" standard.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
Vincent Lefevre writes:
> On 2015-03-21 13:14:08 -0700, Russ Allbery wrote:
>> Correct. The Policy statement is about preserving user changes, not
>> about never touching any file that a user has modified in any way. The
>> package is free to modify unchanged portions of t
er
the benefit of the change is worth the disruption of changed behavior on
upgrades.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87egoif6r3@hope.eyrie.org
x27;t set) is to
use www-browser.
> How to solve this problem? Simply by asking managers of packages of
> graphical browsers to point to the correct virtual package
> (x-www-browser)?
> Is this appropriate?
All this stuff badly needs to be documented in Policy, and then we can
point mai
ke some progress.
+1.
I use help as a sort of variant of wontfix. It means that I'm not opposed
to a fix for that bug, but I'm not going to work on it, either because I
don't have the time or I don't have the necessary skills. Therefore,
unless someone else works on it, it&#
ued, not
> sent, so it shows up via 'mailq' and can be removed via 'exim4 -Mrm
> ' so that it won't get sent when setting the QUEUERUNNER
> back to 'combined'.
I believe this is a per-user default, so if you had previously run
reportbug on that system, y
Joseph Herlant writes:
> Reportbug sends mails via your local mail server by default.
Pretty sure this isn't true any more, is it? I think it's now using the
submit port and sending mail directly to a Debian host. (Of course,
that's unstable/testing; stable may be too old fo
context?
> Dpkg::Arch::get_valid_arches, which looks at /usr/share/dpkg/*table
I'm pretty sure that Lintian already uses that data to check whether
architectures are valid (I vaguely remember working on that code), but it
may well be that the existing check doesn't get t
re of that this morning before I have to go do other work.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.
Package: qa.debian.org
Severity: wishlist
Now that the backports archive has been integrated more completely
into the regular Debian archive, it would be great to see uploads
to backports show up in the news section of the PTS.
-- System Information:
Debian Release: jessie/sid
APT prefers testi
no way inside the protocol to redirect the client.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: h
uch better at ignoring things they've
been told to ignore than humans are. (More implementation work, though.)
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "
Paul Wise writes:
> On Sat, Feb 9, 2013 at 6:14 AM, Russ Allbery wrote:
>> Given that it's reporting failures, personally I'd kind of like to have
>> it in todo, but maybe there aren't enough people who are interested
>> yet?
> Probably "problems&
om the PTS point of view, clang is yet another buildd
> toolchain.
Given that it's reporting failures, personally I'd kind of like to have it
in todo, but maybe there aren't enough people who are interested yet?
--
Russ Allbery (r...@debian.org) <http://www.eyrie
L, for
example), but that starts feeling kind of silly.
I suppose another possibility is to define the deb822 field value as
having as its contents a nested deb822 document and do something like:
References:
Author: Name Surname
Url: http://example.org/
.
Author: Other Name
mats and two different parsers in code that operates
on Debian packages is worth the benefits of YAML.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87hamwvz2e@windlord.stanford.edu
Paul Wise writes:
> On Fri, Jan 4, 2013 at 12:59 AM, Russ Allbery wrote:
>> Of course, the other issue that this DEP raises is how much sense it
>> makes to put all this stuff in the source package, either in
>> debian/control or in a new file, given that most of these fiel
run it would be nice if it would take over some of the
metadata requirements of debian/copyright (all the stuff that isn't actual
legal notices, basically). We currently have that information spread
across multiple files; if we're going to go to the work of introducing a
new file
the additional tag
types), it was apparently fairly easy to change the consumers.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
eze. If we would want
> different or less messages on PTS during freeze, then this goes wider
> than just the messages about standards-version. Is this a good summary
> of what we discussed so far ?
Sounds right to me.
--
Russ Allbery (r...@debian.org) <http://www.eyrie
ersion without
> further changes is not wrong.
I'm happy to go with this policy if the release team is okay with it. My
understanding is that they'd rather people not do this, which is where my
hesitation comes from.
--
Russ Allbery (r...@debian.org) <ht
e.
However, I must admit that, other than as demostrations of strict
standards compliance, I've never met a mail system in the real world that
delivered varient capitalizations to different people. I've heard of some
that bounced some capitalizations as an anti-spam measure, but that
people who discuss this sort of thing on debian-mentors.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas
rinciple (even apart from the issue of requiring network
access).
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.
m tarball, since
dpkg-source doesn't agree with that. If you make the debian directory at
the same level as SAINT_v2.3.3 and __MACOSX, everything, including quilt,
will work (although of course you'll have to change the packaging to
actually work in the SAINT_v2.3.3 directory).
sn't actually use quilt, though; it uses its own
internal, mostly-compatible logic, which is simpler than everything that
quilt can do.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a
hable over a longer period, like a week.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87vckmfp4g@windlord.stanford.edu
available: 4.1.0, you should consider
packaging it.
but per the top of news:
[2012-03-17] Accepted 4.1.0-1 in unstable (low) (Russ Allbery)
(which was five days ago).
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (
ke NMU
detection would break and the actual identity of the maintainer isn't
preserved in the package metadata, both of which I think are important.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-qa-requ...@list
t gone.
We're currently instead in a similar bubble around cloud computing, and
I'm sure we could get quite a few donations from cloud companies for
similar reasons, but unfortunately those donations are much harder for
Debian to use since they don't have the same sort of on
aging area, or some combination of the two. I
don't really want us to go hog-wild with lots of additional Lintian add-on
packages, since that could make things a bit confusing. We may even want
to build everything from the Lintian source package, and just break things
out into separ
hem.
I point users at the PTS all the time. They contain really valuable
information for anyone running Debian that isn't available anywhere else.
The PTS is usually a better overall view of a package for someone who
knows something about Debian and is looking for specific details than
package
! Thank you. That may well be what's going on.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
erned with, so they're unrelated to the acceptance of your package.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
e curret DDPO table goes
*well* off the right edge of the screen for me on a 1680x1050 display,
which is not exactly a netbook. Nine columns (everything from binary
packages on) are entirely off the side of the screen. And that's not with
what I consider a very large font.
--
Andreas Tille writes:
> On Mon, Jul 12, 2010 at 04:32:15PM -0700, Russ Allbery wrote:
>> Well, I think it's just capturing everything in the Sources list.
>> Having that consistency where everything is captured does seem like a
>> nice feature to me.
> Lucas answer
s-perl | perl | main |
> mailto:r...@debian.org
Whoops, that's a bug. Forgot to fix that before I uploaded the private
package I'd been maintaining to Debian proper. Thanks!
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
reebsd ones where the recommended package
> doesn't exist.
That's not a meaningful thing to do for an arch: all package. You should
always get the same arch: all package regardless of the build
architecture, or it's not really arch: all.
--
Russ Allbery (r...@debian.org)
it, which hurts the
project for all the things that Lintian looks at that aren't
controversial. Because of that, Lintian tends to be fairly conservative
on anything that people seem to be debating (although we don't always
manage).
--
Russ Allbery (r...@debian.org) <http://
anually copying out the configuration file. If purging
the package deletes databases, this removes that tactic as an option.
* Whether it makes sense given Debian semantics or not, users just don't
expect removing packages to, from their perspective, destroy data.
Other distributi
Manoj Srivastava writes:
> On Sun, Jan 03 2010, Russ Allbery wrote:
>> and what the requirements of a package are around preserving or
>> removing its data other than log files and configuration files on
>> purge? If so, that would be the relevant place to talk ab
Responding to a message from last April that had been sitting in my
to-process queue.
Holger Levsen writes:
> On Montag, 6. April 2009, Russ Allbery wrote:
>> I don't see much real benefit in going out of our way to remove
>> /var/games and it looks like it would be a bit an
Stefano Zacchiroli writes:
> On Thu, Sep 10, 2009 at 12:57:27AM -0700, Russ Allbery wrote:
>>> Russ (assuming that "info" messages are the only missing ingredient to
>>> implement this given request): would it be problematic to add an extra
>>> column t
able to not allow people to upload packages with
obvious and easily-correctable errors even if they're not must directives,
although I suppose we could implement that by upgrading all such errors
to must in Policy.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle
Package: qa.debian.org
Severity: wishlist
In the versions section of the page, could you also add versions from
backports.org if there are any? This information is available in the
DDPO but not in the PTS right now, which means a separate click through
to check the backports.org version number.
Package: qa.debian.org
Severity: wishlist
In the buildd links on the PTS page for a package, could you also link
to the backports buildd status pages if there's a backported version of
a package? These are at experimental.ftbfs.de/new, which is a hard URL
to find with Google if one doesn't rememb
Lucas Nussbaum writes:
> On 10/09/09 at 14:37 -0700, Russ Allbery wrote:
>> Out of curiosity, how is UDD gathering this data? (I don't want to
>> accidentally break it.)
> Using http://lintian.debian.org/lintian.log
Oh, okay, so it reparses the lintian log. Yeah, th
ow is UDD gathering this data? (I don't want to
accidentally break it.)
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
't already
was that I wasn't sure if I'd break any software that consumed that file.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
s at present.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
, but there are a bunch of
certainty: certain tags with a bunch of overrides, which is clearly
wrong.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
ry
purposes, but it's possible to configure mail software to not do so.
I don't know what this implies about what the QA software should do, but
Lintian, for instance, would not consider those two addresses as matching
because of that standard.
--
Russ Allbery (r...@debian.org)
Sven Joachim writes:
> On 2009-04-06 19:59 +0200, Russ Allbery wrote:
>> I'm curious why it wasn't removed. /var/games is normally shipped in
>> each of the packages that provides files in /var/games, so dpkg would
>> normally remove it automatically once the la
unowned, which implies to me that either some
package created it in a maintainer script rather than just including the
directory in the deb or you're running into the bug that I ran into with
openafs where dpkg lost track of the owner of a directory (I can't find
the bug number at the momen
Lucas Nussbaum writes:
> On 17/02/09 at 20:46 -0800, Russ Allbery wrote:
>> If we're talking about a group of people taking collective
>> responsibility for keeping orphaned packages kicking along, I guess I'm
>> not sure how that differs from what we already have
Sorry, this was actually supposed to go to debian-qa and I failed to pay
attention to what my mail client was doing.
Russ Allbery writes:
> Raphael Geissert writes:
>> Russ Allbery wrote:
>
>>> If I don't have time to do a proper job of maintaining the package, I
&
s would sit in RFA for some time, since often
they're listed there because the DD is no longer personally using the
package, often for reasons that mean the package is being used less in
general.)
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNS
#x27;d be
curious to see the results.
Maybe, similar to low-threshold-NMU, it would work best if it started as
an opt-in system?
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.or
ut for every package they uploaded for pkg-perl.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Ben Hutchings <[EMAIL PROTECTED]> writes:
> On Sat, 2008-11-29 at 13:50 -0800, Russ Allbery wrote:
>> Holger Levsen <[EMAIL PROTECTED]> writes:
>>> currently, mails send to [EMAIL PROTECTED] are only send to the address
>>> listed
>>> in maintain
und it by splitting mail based on the To
and Cc headers instead of the standardized List-Id header, but that's not
as clean.
I have no objections to this being added if there's some way to turn it
off.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
the maintainer is a mailing list and
Uploaders are the people who do the uploads, doesn't it? I generally want
to get such mail only once, via the mailing list.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PR
ng stuff would not reside only on my local disk but in a
> commonly accessible VCS and the location to this VCS is clearly
> mentioned in the VCS fields of the control file.
Why not just use collab-maint for this?
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~e
l avoid bothering you in the future with
> this request :)
Will do.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
lames for a given source package. To
> do that I would need a machine parseable version of the lintian output.
>
> Is there anything like that available somewhere? I wouldn't like having
> to scrape HTML ...
http://lintian.debian.org/lintian.log
--
Russ Allbery ([EMAIL PROTECTED])
kages with no
> severe bugs, with active upstreams, and with a good number of users
> shouldn't be the target of a 'hard' (i.e. preventing it from being
> shipped in stable) cleanup.
The packages you're listing by and large don't meet that criteria.
> DFSG:
>&g
Mika Tiainen <[EMAIL PROTECTED]> writes:
> On 13 Jul 2008, Russ Allbery wrote:
>> This package is useful for emacs21 users, as it's considerably newer
>> than what was included in emacs21. I agree that it's not useful for
>> emacs22 users (and indeed isn&#
ms. I don't believe it's horribly buggy or
unstable, alpha label nonwithstanding.
If emacs21 is going to be removed from the archive before the release, we
may not need this package, provided that the xemacs packages released with
lenny have a newer version.
--
Russ Allbery ([EM
amed references.
>
> But I know nothing about docbook so I can not help reformating all the
> policy.
Indeed, this is exactly why it's hard. (Plus, it's DebianDoc-SGML, not
DocBook.)
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
The links should really be generated automatically somehow (and the
section numbers should be automatically resolved), but this is not at all
easy to do at the moment.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
e's a web variant of "upgrading-checklist.gz"
> contained in the Debian policy.
There is an HTML version of upgrading-checklist in the debian-policy
package source. It's not currently shipped in the package, but we could
add it easily enough. I'm not sure that it&
b5 is a similar case; I think that one is safe to remove.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ow why that
would cause lintian to misdiagnose this tag. It may be easy to fix.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
blems, but those weren't release goals.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tches.
Either they should be applied or the patch tag should be removed from
those bugs.
and:
X bug in the Bug Tracking System is tagged as having a patch. Either
it should be applied or the patch tag should be removed from that bug.
for X == 1.
--
Russ Allbery ([EMAIL PROTECTED
a
user trying to pick between multiple packages that may solve their
problem.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Frank Lichtenheld <[EMAIL PROTECTED]> writes:
> Package: qa.debian.org
> Severity: normal
>
> For the lintian link '-' needs to be converted to '_'
I just need to ugprade lintian on lintian.d.o, since this modification is
really wrong.
--
Russ Allbery (
rg could be fixed
to serve .html.gz files with a Content-Type of text/html and a
Content-Encoding of gzip, which browsers should then cope with. I've
found that adding:
RemoveType .gz
AddEncoding gzip .gz
is sometimes necessary to get Apache to recognize this correctly.
--
Russ Al
Stefano Zacchiroli <[EMAIL PROTECTED]> writes:
> On Wed, Jan 02, 2008 at 04:16:22PM -0800, Russ Allbery wrote:
>> * There are two reports for each maintainer. The one under maintainer,
> What did you decide for the lists related to the two kind of reports we
> discussed in
tim hall <[EMAIL PROTECTED]> writes:
> Russ Allbery wrote:
>> If you want to take a look at how good (or bad) the templates look, the
>> ones that generated those pages are in:
>>
>> /org/lintian.debian.org/lintian-test/reporting/templates
>>
>>
Thijs Kinkhorst <[EMAIL PROTECTED]> writes:
> On Thursday 3 January 2008 01:16, Russ Allbery wrote:
>> http://lintian.debian.org/reports-testing/
>
> This looks good in general, it's a clear improvement over what we have.
Thanks!
>> * The HTML pages are now t
er seen overwrite the report of the previous maintainers. This
particularly affects packaging teams, since our packaging teams have a
regrettable tendency to use many different variations of the team name
in their packages.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.e
Pierre Habouzit <[EMAIL PROTECTED]> writes:
> On Wed, Jan 02, 2008 at 08:04:44PM +, Pierre Habouzit wrote:
>> On Wed, Jan 02, 2008 at 07:58:24PM +, Raphael Geissert wrote:
>>> Russ Allbery <[EMAIL PROTECTED]>
>>>libgss-dbg (U)
>>>shi
the XHTML 1.0 spec and the HTML 4.01 spec both say that
they're fine.
If you want to work around this until the next lintian release, that's of
course fine, but lintian will be fixed so that the current links will
work.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.ey
Stefano Zacchiroli <[EMAIL PROTECTED]> writes:
> On Sun, Dec 30, 2007 at 10:10:35AM -0800, Russ Allbery wrote:
>> Note that you can tell whether a package has lintian warnings or errors
>> based on the contents of <http://lintian.debian.org/reports/qa-list.txt>.
>>
e qa-list.txt as-is and generate a second
full list with more columns, or add more columns to the existing file.
Probably the former to be safe.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
les used
internally by lintian, but it shouldn't be *too* much work.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
up with a weird e-mail address, but the vast majority shouldn't need to be
escaped.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Raphael Hertzog <[EMAIL PROTECTED]> writes:
> On Fri, 21 Dec 2007, Russ Allbery wrote:
>> Okay, lintian is finishing its daily run for today right now, and as
>> soon as that finishes, I'll kick off the full archive run. It should
>> be done sometime on Sat
gt; require an up-to-the minute synchronization ;-)
Okay, lintian is finishing its daily run for today right now, and as soon
as that finishes, I'll kick off the full archive run. It should be done
sometime on Saturday afternoon (US Pacific time), judging from past
experience.
e the breakage in links from the PTS and developer pages,
so I want to coordinate with you a good time to do this. Could you let me
know when would be a good time to do the switch, assuming that the archive
run needs to start about a day and a half in advance of when the new URLs
will be live?
--
et didn't touch the font size
> at all. That way everyone can choose the base font size that suites
> their situation best, once, in the browser config, and every page will
> be good for them.
Yes, exactly. Enthusiastically seconded.
--
Russ Allbery ([EMAIL PROTECTED])
t the most likely result will be that we'll just drop nearly all
GTK 1.0 software from the archive entirely, not that anything that hasn't
already moved to GTK 2.0 will actually do so.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSU
Luk Claes <[EMAIL PROTECTED]> writes:
> So, libglib1.2ldbl, libgtk1.2 and maybe libgd2-xpm would qualify to be
> included?
libgd2-xpm isn't even in oldlibs and there's no hint in the package
description that it shouldn't be used. Is it really being phased out
1 - 100 of 176 matches
Mail list logo
