o? Or am I
mis-remembering?
Regards,
-Roberto
--
Roberto C. Sánchez
Package: wnpp
Severity: wishlist
Owner: Ananthu C V
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: rust-csv2svg
Version : 0.2.1
Upstream Contact: dystroy
* URL : https://crates.io/crates/csv2svg
* License : MIT
Programming Lang: Rust
Package: wnpp
Severity: wishlist
Owner: Ananthu C V
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: rust-names
Version : 0.14.0
Upstream Contact: Fletcher Nichol
* URL : https://crates.io/crates/names
* License : MIT
Programming Lang: Rust
Package: wnpp
Severity: wishlist
Owner: Ananthu C V
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: ruby-cssbundling-rails
Version : 1.4.0
Upstream Contact: David Heinemeier Hansson
* URL : https://github.com/rails/cssbundling-rails
* License
Package: wnpp
Severity: wishlist
Owner: Ananthu C V
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: ruby-googleapis-common-protos
Version : 1.5.0
Upstream Contact: Google APIs <"googleapis-packa...@google.com">
* URL : https://github.com/g
Package: wnpp
Severity: wishlist
Owner: Ananthu C V
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: ruby-gapic-common
Version : 0.21.1
Upstream Contact: Google LLC
* URL : https://github.com/googleapis/gapic-generator-ruby
* License : Apache-2.0
Package: wnpp
Severity: wishlist
Owner: Ananthu C V
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: ruby-omniauth-shibboleth-redux
Version : 2.0.0
Upstream Contact: Bobby McDonald
* URL : https://github.com/omniauth/omniauth-shibboleth-redux
* License
.0
> 1.22.0-3+deb12u2 Changelog
> Changelog unavailable for gst-plugins-base1.0=1.22.0-3+deb12u2 (404 Not
This is #490848
--
Roberto C. Sánchez
Package: wnpp
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I request assistance with maintaining the shorewall package.
The package description is:
Shorewall allows firewall/gateway requirements to be described using
entries in a set of configuration files. It reads those c
Package: wnpp
Severity: wishlist
Owner: "Felix C. Stegerman"
X-Debbugs-Cc: debian-devel@lists.debian.org, f...@obfusk.net
* Package name: apksigcopier
Version : 0.3.0
Upstream Author : Felix C. Stegerman
* URL : https://github.com/obfusk/apksigcopier
Package: wnpp
Severity: wishlist
Owner: "Felix C. Stegerman"
X-Debbugs-Cc: debian-devel@lists.debian.org, f...@obfusk.net
* Package name: kanjidraw
Version : 0.2.0
Upstream Author : Felix C. Stegerman
* URL : https://github.com/obfusk/kanjidraw
Hi!
* Helmut Grohne [2021-06-10 20:00]:
> […]
> Inconsistency
> =
>
> Some maintainer scripts take care to only run `add-shell` for initial
> configuration or for upgrading from an ancient version that didn't call
> `add-shell`. Others call `add-shell` for every invocation of `postin
Hi,
* Helmut Grohne [2021-06-24 08:10]:
> Felix C. Stegerman cautioned that the contents of /etc/shells depends on
> whether the underlying system is /usr-merged.
It also means that on /usr-merged systems e.g. /bin/screen is not a
"valid" shell, but /usr/bin/screen is (even tho
Package: wnpp
Severity: wishlist
Owner: "Felix C. Stegerman"
X-Debbugs-Cc: debian-devel@lists.debian.org, f...@obfusk.net
* Package name: jiten
Version : 1.1.0
Upstream Author : Felix C. Stegerman
* URL : https://github.com/obfusk/jiten
* License
Package: wnpp
Severity: wishlist
Owner: "Felix C. Stegerman"
X-Debbugs-Cc: debian-devel@lists.debian.org, f...@obfusk.net
* Package name: jiten-nonfree-data
Version : 1.1.0
Upstream Author : Felix C. Stegerman
* URL : https://github.com/obfusk/jiten
* Helmut Grohne [2021-06-28 14:46]:
> On Thu, Jun 24, 2021 at 06:12:05PM +0200, Felix C. Stegerman wrote:
> > It also means that on /usr-merged systems e.g. /bin/screen is not a
> > "valid" shell, but /usr/bin/screen is (even though they are the same
> > file), wh
ackage distribution
> security which doesn't really depend at all on transport layer
> encryption.
In this context, it might make sense to describe using HTTPS as the
transport for APT operations is providing "default confidentiality".
Regards,
-Roberto
--
Roberto C. Sánchez
to allow bringing legacy log data
*into* the systemd journal[*] to allow for accessing log data through a
single interface/mechanism after making the transition?
Regards,
-Roberto
[*] whether as part of the transition or as a separate step that can be
executed manually
--
Roberto C. Sánchez
On Sat, Nov 13, 2021 at 10:43:48PM +0100, Michael Biebl wrote:
> On 13.11.21 22:40, Roberto C. Sánchez wrote:
> > On Sat, Nov 13, 2021 at 10:32:23PM +0100, Michael Biebl wrote:
> > >
> > > - Existing systems will continue to have rsyslog installed (but they can
>
On 2/26/22 21:09, Paul Wise wrote:
Control: forwarded -1 https://github.com/donnemartin/gitsome/issues/177
On Sat, 26 Feb 2022 23:43:14 +0800 SZ Lin (林上智) wrote:
The "gitsome" has used "gh" since 2017, and thus would you mind renaming
the "gh" in your package to avoid the conflict issue?
uite like it better from a
visual perspective), and issue a deprecation warning for the old format
(e.g., when -I is specified).
Then perhaps after the next stable release drop the old format.
>
> Thanks a lot for maintaining lintian in any case
>
+1
Regards,
-Roberto
--
Roberto C. Sánchez
age should not be in the archive rather than hand-wavy
arguments without any actual substance. Otherwise, it will appear as
though you are simply attempting to conform everyone else to your own
personal view on things. I think we can all agree that "there are a
*lot* of issues" with such an approach.
Regards,
-Roberto
--
Roberto C. S�nchez
the vast majority of
ITPs actually never elecit any sort of response from anyone), seems
rather pointless.
Filing the ITP then immediately uploading seems really sensible,
especially since in the event of a mistake it is trivial to email
ftp-master requesting a REJECT, which IME is usually something they do
right away.
Regards,
-Roberto
--
Roberto C. Sánchez
On Thu, Jul 14, 2022 at 05:48:56PM +0500, Andrey Rahmatullin wrote:
> On Thu, Jul 14, 2022 at 08:45:24AM -0400, Roberto C. Sánchez wrote:
> >
> > Filing the ITP then immediately uploading seems really sensible,
> More sensible than not filing it?
> This defeats both purposes
bullseye. Are you certain that you have a matching upstream version?
How did you obtain the source package? How are you unpacking it? What
exact commands did you use?
Regards,
-Roberto
--
Roberto C. Sánchez
20PM +0530, Avinash Roy wrote:
>Hi Roberto,
>Thank you for pointing out the error in the subject line. I have fixed
>that and yes it's for bullseye curl.
>The below packages are used to create lib:
>[1]http://deb.debian.org/debian/pool/main/c/curl/curl_7.74
ing /etc/apt/
> trusted.d possible, but now that we have "Signed-By:" it is the inferior
> solution and thus not needed anymore.
>
What is the earliest version of apt that supports Signed-By in
sources.list? I scanned the changelog but it was not immediately clear.
Regards,
-Roberto
--
Roberto C. Sánchez
On Sat, Nov 09, 2019 at 06:23:04PM +, Colin Watson wrote:
> On Sat, Nov 09, 2019 at 12:29:11PM -0500, Roberto C. Sánchez wrote:
> > On Mon, Nov 04, 2019 at 02:27:19PM +0100, Timo Weingärtner wrote:
> > > Maybe apt could deprecate /etc/apt/trusted* and apt-key(8) in b
ould be nice if it became the basis of a new section in the
installation manual (perhaps under section 8, Next Steps and Where to Go
>From Here). It may also be a good addition/improvement to the Securing
Debian Manual.
In any event, I am just offering some thoughts; perhaps they might be of
some use.
Regards,
-Roberto
--
Roberto C. Sánchez
the basis of the FTP
master review and a signed source changes to enter the archive if the
package is approved?
When I build packages I always end up with both changes files, so
requiring both for NEW processing would be a triviality (for me, at
least) and eliminate this peculiarity as well.
Regards,
-Roberto
--
Roberto C. Sánchez
uld you want what has been Debian's goal of being a universal Linux,
> good for so many more?
>
Ibid.
> Let's be positive about this and find a way to be more inclusive of
> the greater Debian population; it should be a win for everyone.
>
There are countless ways for anyone, DD or not, to influence the
direction of the Debian project. So, perhaps all that is needed is to
begin taking advantage of those ways, rather than complaining about the
one way that, for very good reason, is reserved only for DDs.
Regards,
-Roberto
[0] https://www.debian.org/social_contract
--
Roberto C. Sánchez
On Wed, Jan 01, 2020 at 02:09:46PM -0500, Roberto C. Sánchez wrote:
> [stuff]
I just saw Sam's message after I sent my own. I agree that this
discussion has gone past the point where it is useful. Apologies for
the noise.
--
Roberto C. Sánchez
I've read the distro-tracker documentation and it seems like interaction
is by visiting with a web browser or via email. Is there an official or
even unofficial API for access to data in distro-tracker?
Regards,
-Roberto
--
Roberto C. Sánchez
On Fri, Jan 17, 2020 at 02:41:26AM +, Paul Wise wrote:
> On Thu, Jan 16, 2020 at 7:06 PM Roberto C. Sánchez wrote:
>
> > I've read the distro-tracker documentation and it seems like interaction
> > is by visiting with a web browser or via email. Is there an official
irement (i.e., a CLA), but in practice it is likely to irk potential
contributors.
Regards,
-Roberto
--
Roberto C. Sánchez
e
some minor tweaks, but the above are the major steps.
Regards,
-Roberto
--
Roberto C. Sánchez
ere will be a mini-DebConf in Montreal" and so-on and so
forth?
Regards,
-Roberto
--
Roberto C. Sánchez
On Sat, Feb 15, 2020 at 02:41:59PM +0100, Geert Stappers wrote:
> On Sat, Feb 15, 2020 at 08:33:25AM -0500, Roberto C. Sánchez wrote:
> > On Sat, Feb 15, 2020 at 02:16:27PM +0100, Harald Dunkel wrote:
> > > Hi folks,
> > >
> > > I am maintainer for mg, curr
minimize them would
go a long way to reducing the likelihood of flame responses to rejection
mails.
Regards,
-Roberto
--
Roberto C. Sánchez
master' the branch where active development
takes place or does development take place elsewhere and 'master' is the
branch from which releases are made?" A branch called "devel" would
unquestionably be where active development is taking place.
Other branch names could then be chosen based on the needs of the
project, like "test", "stage", & "prod", or "rc" & "release", or
whatever.
Regards,
-Roberto
--
Roberto C. Sánchez
non-future-proof and
> violates all sorts of software engineering principles.
>
> Anybody know if there's a good solution to this problem?
>
A slightly less bad approach might be:
Build-Depends: julia [! ! ...], clang [! ! ...]
Regards,
-Roberto
--
Roberto C. Sánchez
.
>
I have had good results with snapshot.debian.org. On a few occasions,
simply downloading each successive version from snapshot.debian.org and
then using something like 'gbp import-dscs *.dsc' gives more than
sufficient version history. Granted, that has limitations, but it is
available right now.
Regards,
-Roberto
--
Roberto C. Sánchez
On Wed, Aug 19, 2020 at 04:33:28PM +0500, Andrey Rahmatullin wrote:
> On Wed, Aug 19, 2020 at 07:31:08AM -0400, Roberto C. Sánchez wrote:
> > > For non actively maintained packages on could check them into Git
> > > oneself and then start a history from there, and p
Package: wnpp
Severity: wishlist
Owner: "Roberto C. Sanchez"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: libmongocrypt
Version : 1.0.4
Upstream Author : Mongo C Driver Team
* URL : https://github.com/mongodb/libmongocrypt
quot; to itself be somewhat
disturbing. You cannot possibly know what grounds someone might have
for not wanting systemd, and to automatically and universally
characterize that as "disturbed" implies a value judgment that runs
counter both to the freeness and universailty that Debian as a project
espouses.
Regards,
-Roberto
--
Roberto C. Sánchez
o trigger the
use of -J in place of -j. At least, that is the case on stretch. Is
there an easy way (preferrably via environment variables) to achieve
that?
Regards,
-Roberto
--
Roberto C. Sánchez
and would definitely get involved, time permitting.
Regards,
-Roberto
--
Roberto C. Sánchez
trated by it. In the university
class I teach, dependency management in our project is something that is
quite important. Though, at that stage of life, the students usually
lack the experience to appreciate why it is important.
Regards,
-Roberto
--
Roberto C. Sánchez
ready does "security by upstream releases" for Firefox,
> and this clearly shows why this is problematic:
Also PostgreSQL, formerly MySQL, OpenJDK, etc. Some go smoothly (I think
PostgreSQL upstream is very good here), and some do not.
Regards,
-Roberto
--
Roberto C. Sánchez
problems. That
said, the problems are not really any different than the problems
introduced by installing components with cpan or pip and then forgetting
about them.
Regards,
-Roberto
--
Roberto C. Sánchez
not to mention 'salts',
'stilts', and who knows how many other words in the English language.
If we are going to start applying this sort of logic to naming, then
there are plenty of other places (e.g., where actual vulgarities are
used in package names, where abreviations and/or acronyms create words
that are or can be perceived as offensive, etc.).
Regards,
-Roberto
--
Roberto C. Sánchez
.
>
> No, this is no reason to introduce such sequence points. You don't even
> know that the MTA runs on the same system.
>
Unless it is designed to only interact with an MTA running on the same
system.
Regards,
-Roberto
--
Roberto C. Sánchez
alidating the
relationships between packages).
There are plenty of available tools to identify system cruft, including
packages that are no longer receiving security support and packages
which do not exist in the current suite/release for which the system is
configured.
Regards,
-Roberto
--
Roberto C. Sánchez
and then subsequently deleted lots of messages that by
any objective measure would have served to only worsen a situation. When
I have failed to follow my own advice, I have without fail only made the
situations in question worse.
Regards,
-Roberto
--
Roberto C. Sánchez
where maintainer like '%,%'
> order by maintainer;
> maintainer
>
> ------
> "Adam
ot;close
enough" for the purposes of the maintainer/uploader fields in the
control file. However, there is a high likelihood that enough of them
are different enough to be problematic from the perspective of a
heterogeneous tooling infrastructure.
Regards,
-Roberto
--
Roberto C. Sánchez
if any, should be made buggy by this change.
>
>Where can i read debian's FHS 3.0?
>I can only see 2.3 on [1]https://www.debian.org/doc/packaging-manuals/fhs/
It is kind of a pain to locate. Here is the link:
https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf
Regards,
-Roberto
--
Roberto C. Sánchez
self and others in the spirit in which it was intended: to help you
produce a better free software tool and to improve as a developer.
Regards,
-Roberto
--
Roberto C. Sánchez
d and identified, even if it has never manifested itself in
the real world. If you doubt that, please review the recent news
surrounding the SPECTRE and MELTDOWN vulnerabilities.
Regards,
-Roberto
--
Roberto C. Sánchez
r just PM me directly please?
>
https://wiki.debian.org/Keysigning/Offers#US
There are three Debian Developers listed as offering to sign keys in San
Francisco. That should get you started.
Regards,
-Roberto
--
Roberto C. Sánchez
Package: wnpp
Severity: wishlist
Owner: "Felix C. Stegerman"
* Package name: mmm
Version : 0.4.1
Upstream Author : Felix C. Stegerman
* URL : https://github.com/obfusk/m
* License : GPLv3+
Programming Lang: Python
Description : minimali
n=4
> opts="mode=git,pgpmode=gittag" \
> https://github.com/rs/net-server-mail refs/tags/v([\d\.]+) debian
>
Wow! That is very nice. Thanks for the hard work.
Regards,
-Roberto
--
Roberto C. Sánchez
buted/signed with a
> key we trust.
>
I have encountered this same situation and have resorted to backporting
packages from testing/unstable myself :-/
>
> Will there be a proper solution for that soon?
>
I hope that there will be.
Regards,
-Roberto
--
Roberto C. Sánchez
On Fri, Dec 01, 2017 at 05:31:09PM +0100, Alf Gaida wrote:
> >
> Ian, thats dead easy - put the needed packages onto the iso and be done
> with. The installer should have an option to opt-in contrib and/or
> non-free. Done. Ok, that was the technical part.
Which has the potential to make the insta
Package: wnpp
Severity: wishlist
Owner: "Roberto C. Sanchez"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: sword-comm-mhc
Version : 1.6
Upstream Author : The SWORD Project
* URL : http://crosswire.org/sword/modules/ModInfo.jsp?modName=MHC
Package: wnpp
Severity: wishlist
Owner: Ananthu C V
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: python-ratelimit
Version : 2.2.1
Upstream Contact: Tomas Basham
* URL : https://github.com/tomasbasham/ratelimit
* License : Expat
Programming
Package: wnpp
Severity: wishlist
Owner: Ananthu C V
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: python-datadog
Version : 0.50.1
Upstream Contact: Datadog, Inc.
* URL : https://github.com/DataDog/datadogpy
* License : BSD-3-Clause
Programming
Package: wnpp
Severity: wishlist
Owner: Ananthu C V
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: python-simplepush
Version : 2.2.3
Upstream Contact: Timm Schaeuble
* URL : https://github.com/simplepush/simplepush-python
* License : Expat
On Wed, Dec 18, 2024 at 09:06:48PM +0200, Wouter Verhelst wrote:
> reportbug can send emails through sendmail (if you have that
> configured), or it can be set up so it can bypass that entirely and send
> email directly to an SMTP server.
If you use something like thunderbird, you can always do so
On Sat, Mar 15, 2025 at 05:23:54PM -0400, Jeremy Bícha wrote:
> On Sat, Mar 15, 2025 at 4:34 PM Roberto C. Sánchez wrote:
> > Question: Should uncoordinated NMUs unilaterally choose Salsa as the VCS
> > for a package?
>
> Why are you opposed to using Salsa as the VCS for cp
Hi,
I am not entirely sure, but I think you can probably find those missing
timezones in tzdata-legacy package.
Best,
Ananthu
Us is discouraged.
I had thought of possibly suggesting an update to the documentation, but
I'm not sure that adding more words would make the matter any more
clear.
How do others suggest to handle this particular situation?
Regards,
-Roberto
--
Roberto C. Sánchez
meout. Reconnect.
> Sorry.
>
> Is it just me?
I uploaded on Monday using the ssh-upload target. Have you tried that
one?
Regards,
-Roberto
--
Roberto C. Sánchez
occurence of that sort of thing. And, yes, CVE is probably not a great
proxy. But Santiago has discussed this with quite a few of us on the LTS
team at various points along the way, and a better proxy hasn't been
found.
Regards,
-Robeto
--
Roberto C. Sánchez
te that in the bug report. So, then someone wouldn't have
to ask, it would already be stated that you are waiting for some
specific reason.
Perhaps the way to look at it is that in the case where isn't directly
helpful to the maintainer (as in your specific case), it can be helpful
to those with a desire to collaborate in some way.
Regards,
-Roberto
--
Roberto C. Sánchez
hing like 'old-debian-branch') which it then warns the user about
when the two branch pointers aren't pointing at the same commit. Or
something like that.
Regards,
-Roberto
--
Roberto C. Sánchez
Hi,
On 14 May 2025 09:29:23 UTC, Simon Josefsson wrote:
>PICCA Frederic-Emmanuel
>writes:
>
>>> There is the Source field in d/copyright where you can put a git remote
>>> URL. Maybe that usage should go into DEP-14 ?
>>
>> So we have upstream informations in
>>
>> d/copyright
>> d/control (git
kage is maintained in Salsa, and there
is recent activity, then that is probably a good way to interact with
the maintainer. But absent that (either because the project in Salsa
doesn't permit all DDs push access or because it's simply not in Salsa),
the guidance from devref seems to cover the situation rather well.
Regards,
-Roberto
--
Roberto C. Sánchez
latform (especially if they handle the
administration), why wouldn't we accept?
Regards,
-Roberto
--
Roberto C. Sánchez
On Fri, May 23, 2025 at 03:58:34PM +0100, Colin Watson wrote:
> On Fri, May 23, 2025 at 10:00:22AM -0400, Roberto C. Sánchez wrote:
> > But it could be an option. If Atlassian offered the Debian project free
> > (gratis) use of their platform (especially if they handle the
> >
quot; before moving towards a GR, and he is being told that
he is wrong and that he should have gone for a GR.
We should probably decide which way is "right".
Regards,
-Roberto
--
Roberto C. Sánchez
that jokes of such a nature must be deplored but then also
that their use against some groups is acceptable.
Am I, as a member of a marginalized group, not permitted to make jokes
about my own group? If that's the case, no thanks, I don't need someone
telling me that I can't make fun of myself or of others in my group.
Regards,
-Roberto
--
Roberto C. Sánchez
Should we start purging those as well?
And of course, the bug reports which Salvo referenced in his initial
email are clear evidence of the Community Team acting in ways that we
have been repeatedly assured they do not act. So much for those
assurances.
Regards,
-Roberto
--
Roberto C. Sánchez
e, even if
> they're not marginalized in their present locale, and adjust policies
> accordingly.
Or a simpler solution: judge individuals "by the content of their
character." As a famous Christian minister once said [0].
[0] https://en.wikipedia.org/wiki/I_Have_a_Dream
--
Roberto C. Sánchez
likelihood
that discussions like this will be repeated (as Russ pointed out that
they are with some regularity).
Regards,
-Roberto
* This would include things like "who is allowed to be offended?" "what
are they allowed to consider offensive?" "who is allowed to judge
whether a claimed offense is genuine?" etc.
--
Roberto C. Sánchez
v 14, 2005 at 05:13:47PM -0500, Adam C Powell IV wrote:
>
> > > And thats what I asked for, yes. Drop the version from -dev|-dbg|-doc,
> > > use the shlib system for the rest (which makes packages built against it
> > > depending on the right version) and have fun.
>
On Tue, 2005-11-15 at 23:03 -0800, Steve Langasek wrote:
> On Tue, Nov 15, 2005 at 05:15:28PM -0500, Adam C Powell IV wrote:
> > On Mon, 2005-11-14 at 23:59 -0800, Steve Langasek wrote:
>
> > > > I understand that, and the whole proposal. And it will break a lot of
>
On Sat, 2005-11-19 at 00:22 -0800, Steve Langasek wrote:
> On Wed, Nov 16, 2005 at 10:53:57AM -0500, Adam C Powell IV wrote:
> > > > > For that matter, why is it important that Debian provide support for
> > > > > coinstallability with older packages that are, ev
On Sun, 2005-11-20 at 17:50 -0800, Steve Langasek wrote:
> On Sun, Nov 20, 2005 at 06:57:36PM -0500, Adam C Powell IV wrote:
> > > Well, I think the factor there is that we "usually" want users to upgrade
> > > to
> > > the latest kernel automatical
On Mon, 2005-11-28 at 15:11 -0500, Adam C Powell IV wrote:
> On Sun, 2005-11-20 at 17:50 -0800, Steve Langasek wrote:
> > On Sun, Nov 20, 2005 at 06:57:36PM -0500, Adam C Powell IV wrote:
> > > > Well, I think the factor there is that we "usually" want users to
> &g
On Thu, 2005-12-15 at 15:05 +1000, Anthony Towns wrote:
> On Wed, Dec 14, 2005 at 09:29:11PM -0500, Adam C Powell IV wrote:
> > Did you receive this email or any of this thread? It's now more than
> > two weeks old, and I'd really like to upload a new PETSc 2.3.0 AS
Greetings,
About two weeks ago (or perhaps earlier, I don't know),
anonymous-ftp-master stopped functioning as an upload host. I think
this corresponded to a dupload upgrade (2.6.3 in testing), since the
$default_host line was commented reflecting a new dupload.conf.
Has anyone else had this pro
On Tue, 2005-04-05 at 11:16 -0500, Gunnar Wolf wrote:
> Adam C Powell IV dijo [Tue, Apr 05, 2005 at 09:55:53AM -0400]:
> > Greetings,
> >
> > About two weeks ago (or perhaps earlier, I don't know),
> > anonymous-ftp-master stopped functioning as an upload host. I
Package: wnpp
Severity: wishlist
Greetings,
I am planning to package libMesh [1], a C++ library for parallel finite
element calculations using MPI, PETSc and (Par)Metis (and possibly hypre
via PETSc). It is actively developed at the University of Texas at
Austin and Hamburg University of
On Thu, 2006-11-23 at 13:28 +1100, Andrew Donnellan wrote:
> On 11/20/06, Adam C Powell IV <[EMAIL PROTECTED]> wrote:
>
> > Second, I may need some advice on the license:
> >
> > Copyright (c) 2001-2003, ETH Zurich and Roman Geus
> > All rights reserved.
>
Greetings,
Please tell me if I have this right:
* You don't like .la files
* So you're unilaterally removing them from a core package
(libxcursor) with dozens of reverse-depends, breaking all of
them
* Even though they're a years-old and very well established
On Thu, 2006-04-13 at 11:12 -0400, Adam C Powell IV wrote:
> Greetings,
>
> Please tell me if I have this right:
> * You don't like .la files
> * So you're unilaterally removing them from a core package
> (libxcursor) with dozens of reve
On Thu, 2006-04-13 at 19:12 +0300, Daniel Stone wrote:
> On Thu, Apr 13, 2006 at 11:12:06AM -0400, Adam C Powell IV wrote:
> > Please tell me if I have this right:
> > * You don't like .la files
>
> Yes.
>
> > * So you're unilat
On Thu, 2006-04-13 at 19:58 -0400, David Nusinow wrote:
> On Thu, Apr 13, 2006 at 07:09:55PM -0400, Adam C Powell IV wrote:
> > *Think* for a moment about the consequences. This is not a simple
> > rebuild, this is a serious problem.
>
> I agree and I take full responsibili
Greetings,
Installing a new kernel package can be a bit of a pain, especially for
newbies, what with hand-editing lilo.conf or config files for other
bootloaders, from grub to yaboot/quik, aboot, palo, you name it. Yes,
the kernel-image postinst runs lilo, but lilo.conf is invariably out of
date,
901 - 1000 of 1041 matches
Mail list logo
