Hi,
Hope I am not writing to wronga aaddress. I am nice, pretty looking
girl. I am planning on visiting your town this month. Can b
we meet each aother in person? Message me back at [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contac
Package: general
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* W
de. We have benefitted repeatedly from his careful
analysis.
--
Sean Whitton
yet I may have a stab at it.
>
> If anyone has any spare cycles I'd also like us think about how a
> full-blown git-filter-branch/-repo invocation would fit into the picture so
> perhaps the interface could handle those in the future.
I do a manual 'git rm', commit, an
Yes, tag2upload. It’s almost ready :)
Please wait a little longer.
--
Sean Whitton
Please excuse top-posting and brevity. I am writing to you from a mobile phone.
> On 1 Aug 2024, at 20:43, Charles Plessy wrote:
>
> Le Thu, Aug 01, 2024 at 12:23:43PM +0100, Luca Boccass
nt
for these sorts of choices.
--
Sean Whitton
le importing into salsa as you also
suggest.
--
Sean Whitton
signature.asc
Description: PGP signature
include some explanations as to what sort of packages are
best suited to each of them.
--
Sean Whitton
signature.asc
Description: PGP signature
to note that once people are using tag2upload, this information
will start being recorded on salsa, as a side-effect. I've filed
#1078016 about exposing this information in a machine-readable way.
--
Sean Whitton
signature.asc
Description: PGP signature
it could be a metadata field.
Just to note that once people are using tag2upload, this information
will start being recorded on salsa, as a side-effect. I've filed
#1078016 about exposing this information in a machine-readable way.
--
Sean Whitton
-dpm, though it is a bit
fiddly to dig it out.
--
Sean Whitton
signature.asc
Description: PGP signature
Hello Santiago,
What are your current intentions in this area? Do you want to make the
change for trixie? If not, I'd like to close the override change bug
for now. Thanks.
--
Sean Whitton
(by the way, after reading the package description, I lowered the
priority of isc-dhcp-common too)
--
Sean Whitton
signature.asc
Description: PGP signature
thing in /usr outside of placing their pre-packaged
files in there[1]. if this information is variable state, then it should
go where variable state information is supposed to go, no question about
it. if the admin should be able to edit it, there's a place for that
too. neither of these is
nalize the api. after that,
i suppose it will be time to start looking for vict^H^H^H^Hvolunteers
to try the setup with their packages.
i'd encourage those with a vested interest in this to take another look
at the "best practices" page and the two packages.
as alwa
Luke Kenneth Casson Leighton wrote:
i'm forwarding this to debian devel for people's attention because
it would appear that debian has lost a quite large opportunity -
by not having selinux available.
PR choices, not much else. It is also entirely possible the last of the
Debian faithful have left
Andreas Tille wrote:
On Thu, 28 Oct 2004, Simon Huggins wrote:
Is this a Transmeta Crusoe based laptop?
No. It is centrono based and I guess this is rather a problem of some pure
X applications, because Gnome and KDE applications and also Mozilla are
behaving fine. The only thing is that sometime
On Mon, Nov 01, 2004 at 08:04:14AM +0100, Marc Haber wrote:
> Why is the information given during package installation stored
> persistently in the first place?
it's not stored persistently, that's why it's in /var/cache :)
sean
--
signature.asc
Description: Digital signature
Package: wnpp
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* Package name: coaster
Version : 0.1.1
Upstream Author : Bryan Forbes <[EMAIL PROTECTED]>, Sean Harshbarger <[EMAIL
PROTECTED]>
* URL : http://www.coaster-burn.or
can't install it! :)
sorry, couldn't help it...
sean
--
signature.asc
Description: Digital signature
Package: wnpp
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package name: dbconfig-common
Version : 0.7
Upstream Author : sean finney <[EMAIL PROTECTED]>
URL :
http://people.debian.org/~seanius/policy/dbconfig-common.html
L
t in
experimental first and get somebody other than me to actually use it.
sean
--
signature.asc
Description: Digital signature
e packages
list hasn't been updated since then. anyway, feedback and thoughts
are welcome.
sean
--
signature.asc
Description: Digital signature
On Thu, Dec 02, 2004 at 12:03:27PM -0500, Simon Law wrote:
> On Thu, Dec 02, 2004 at 11:47:38AM -0500, sean finney wrote:
> > please, please treat this machine politely. it's my workstation and
> > i have no qualms with turning off slapd if it's getting in the
> &
ommon framework?
the big question in my mind is what about the package needs
administrative access? this might stem from my not understanding
differences between mysql and postgresql.
sean
--
signature.asc
Description: Digital signature
On Thu, Dec 02, 2004 at 07:08:17PM -0500, Daniel Burrows wrote:
> On Thursday 02 December 2004 11:47 am, sean finney wrote:
> > exponentially faster
>
> How, exactly, is this "exponentially faster"? Is it guaranteed to run in
> logarithmic time relative to a norm
e control whether or not it actually
starts (i think somebody else has mentioned this too).
sean
--
signature.asc
Description: Digital signature
ot;. with pre-configuration, it is
true that you can't rely on any dependencies being met, but touching
files in the .config script is generally a bad practice, and i don't do
anything other than ask debconf questions in the config script.
sean
--
signature.asc
Description: Digital signature
however, you have to take the database
down in order to do it, which isn't really acceptible imho.
sean
--
signature.asc
Description: Digital signature
dy else has mentioned this too).
>
> Yes, I know such solutions but don't like them much. But if "my"
> solution is proved to be wrong, I'll implement such a workaround...
what's so bad about such a solution? i think it's simple to implement,
easy to unders
would be happy to take this one over. at
some point i even wrote up some code to help transition people from
the version in woody, which i could probably dig up.
sean
--
signature.asc
Description: Digital signature
t;
> yes. Please take it.
okay, when i return from VAC in three days i'll start packaging the new
upstream release for it, and take over the package with a new upload.
have you filed an O: bug against it?
sean
--
signature.asc
Description: Digital signature
on't modify configuration files of other
packages.
sean
--
signature.asc
Description: Digital signature
#x27;t finished packaging the new upstream version, but am actively
working on it, albeit somewhat slowly. would you like me to follow
up with you when i have, or would simply closing the wnpp bug
be enough?
sean
--
signature.asc
Description: Digital signature
the packager was told
the same thing:
http://lists.debian.org/debian-devel/2004/11/msg00553.html
might i suggest something like "gnome-player"?
sean
--
signature.asc
Description: Digital signature
> be needed at boot time before udev is initialized.
how does /.dev fit in with the fhs?
sean
--
signature.asc
Description: Digital signature
On Wed, Feb 09, 2005 at 10:46:29PM +0100, Marco d'Itri wrote:
> On Feb 09, sean finney <[EMAIL PROTECTED]> wrote:
>
> > how does /.dev fit in with the fhs?
> It does not, but there is no other place to put it. Just do not look at
> it and it will not bother you.
tha
static /dev.
that hardly sounds like a necessity then. why not defualt it to
off, and put instructions or commented out code in the init script?
sean
--
signature.asc
Description: Digital signature
g i have open
against mysql-server. christian: any chance of getting an openssl enabled
version of the mysql-client and mysql-server packages?
sean
--
signature.asc
Description: Digital signature
there is a serious security
breach, et c, the new key could be brought out, used to sign a new backup
key (which would be placed back in the lockbox), the package providing the
key could be updated, and life could happily go on.
sean
--
signature.asc
Description: Digital signature
makes the most sense. at least for the time being.
sean
--
signature.asc
Description: Digital signature
put much thought into is how this package
should handle the pre-existing pwc module found in 2.6.8 and earlier.
i guess a conditional diversion should be added? i'll file a phony
rc bug against pwc to keep it out of sarge until this can be
handled properly.
sean
--
signature.asc
Description: Digital signature
speed it up...
sean
(note, this query *should* return no results, i'm just surprised by the delay)
sativa[~]16:49:30$ time ldapsearch -x -h bugs.debian.org -b
dc=bugs,dc=debian,dc=org '(&(debbugspackage=wuzzah)(debbugsstate=open))'
debbugsid
# extended LDIF
#
# LDAPv3
d the
previous version of the package will be totally broken when the other
is updated.
comments would be appreciated... thanks.
sean
--
signature.asc
Description: Digital signature
minati are going to come out
of hiding just to answer this question, i guess i'll upload, find out,
and report back :/
sean
--
signature.asc
Description: Digital signature
file, as opposed to the entire mailbox. in some of the
sloppier imap servers (*cough* uw-imap *cough* *cough*), this can cause
huge, grind-your-server-to-a-halt performance hits as deleting, or
merely reading a new message necessates a huge amount of i/o.
sean
--
signature.asc
Description: Digital signature
> I thought it was "illegal" to modify a message.
marking a message as read is one example. moving a message from one
mailbox to another is another example. although it's not modifying the
message itself, it's moving its location, which with a crappy imap
server can mean
y and read-only, then
mbox is the best way to go, for reasons you mentioned. it sucks
for just about anything else though.
sean
--
signature.asc
Description: Digital signature
as
slightly in-cheek when i said that. it was also slightly not in-cheek,
as i do feel that the world of ftp-master is often shrouded in a veil
of secrecy. however, i by no means meant to offend anyone personally
and if i have i withdraw the comparison.
sean
--
signature.asc
Descri
Jesus Climent wrote:
What would people think about adding a check on all the *dm managers (read
kdm, gdm and friends) about cheking the kernel command line from /proc/cmdline
and grep for nox?
I have the need some times to start a laptop with console mode, and it would
be nice to just add an append
path from the previous version works for folks.
thanks,
sean
--
signature.asc
Description: Digital signature
s i'll upload, find out,
> > and report back :/
>
> Please, do it (report back). I'm interested in the same question.
looks like it works, as long as the binary packages have the same name
you can split a source package into two source packages without having
to traverse new.
script code is whole
heartedly encouraged to check this out!
sean
[1] http://lists.debian.org/debian-devel/2004/10/msg00340.html
[2] http://lists.debian.org/debian-devel/2004/10/msg00962.html
[3] http://people.debian.org/~seanius/policy/dbconfig-common.html
--
signature.asc
Description: Digital signature
http://people.debian.org/~seanius/policy/examples/ ./
you want version 1.4.
thanks,
sean
--
signature.asc
Description: Digital signature
ript).
> I suspect your package should be either supercede wwwconfig-common or
> be rolled into it.
this supercedes what's in wwwconfig-common. in fact, much of the
underlying internal code is taken from or at least originally based
on code from that package.
sean
--
sig
his actually provide any extra security as opposed to having the key
> mounted for the entire session?
i have a usb/hotplug/ssh-add script that loads an ssh key off of a usb
stick, and removes it when the usb stick is removed. if you're
interested i can send you a copy off-list.
ate someone else taking a look at it.
also, i'm not sure whether it still works on 2.4 kernels, i haven't had
a 2.4 machine to test on in a while.
sean
--
signature.asc
Description: Digital signature
h
before i ask anyone to translate it though :)
> I promise you'll soon get tons of translations in
> various languages and I'll personnally give some push so that
> translators know this is a really important thing to translate.
thanks!
sean
--
signature.asc
Description: Digital signature
On Tue, Mar 08, 2005 at 10:51:48PM +0100, Christian Perrier wrote:
> Comments about the templates:
wow... thanks for all these. i'll work on incorporating these suggestions
in with the next version, before i make a request for translations.
sean
--
signature.asc
Des
ound is to remove and re-insert
the key :).
> o a /dev/udev.d file which is run after the node is created that does
> the necessary root-level setup and then calls
>
> o a user-specific script which loads the keys (and prompts for necessary
> passwords) etc.
better watch o
ill sufficiently complicated
it might make sense to have an Arch: all cron-common type package.
sean
--
signature.asc
Description: Digital signature
sers that might not want an
> active cron job. Take 'sac' for example, a user that installs sac,
> installs a tool to do something, he doesn't necessarily want a cronjob to
> send sac's output to him weekly, for example.
i would argue then that user should use a tool
some time back for an packages->LDAP
gateway i threw together[1]. at the time there didn't seem to be much
interest by other people, so i haven't worked on it in several months.
sean
[1] which could hypthetically allow apt-get update to only need to fetch
changed package
of which is currently sitting in the NEW queue ...), the agent
> itself is perfectly useable with gnupg 1.2.
then i'm wondering why someone hasn't packaged it already :)
sean
--
signature.asc
Description: Digital signature
w version of some
library already present in debian. if that's the case, i don't think
this will fly at all.
that said, there's nothing wrong with hosting binary packages somewhere
else and if you do so without breaking my system i'll try them and
build support for gpg-age
ave to move the databases, i'd recommend against hard
coding where you put it. give the admin the option of where to put it.
he/she will know much more about where there's free space to put it.
hth,
sean
[1] http://people.debian.org/~seanius/policy/dbapp-policy.html
--
signature.asc
Description: Digital signature
here's free space to put it.
>
> Yes, another debconf question :((
you could do something like
- use low priority to prompt for the location (so most folks won't see it)
- dump the database
- if failure dumping, display a debconf note saying why the dump failed
(full disk), and that setting debconf priority to low and reinstalling
the package will give the option of where to dump.
sean
--
signature.asc
Description: Digital signature
issue, i'd gladly sponsor a gpg-agent.
sean
--
signature.asc
Description: Digital signature
ed gnupg version 2? this
smacks of the infamous redhat gcc release...
> > assuming james is okay with it and there isn't some kind of library
> > dependency issue, i'd gladly sponsor a gpg-agent.
> >
> Umm, s/sponsor/push it through NEW already, dammit/ ;-)
a
es under an xterm)
sean
--
signature.asc
Description: Digital signature
owerpc" and "ppc64" is inconsistent.
and deviating from an already established standard isn't? i'm wondering
what the actual benefits of having a similarly (powerpc/powerpc64)
named port are, apart from being aesthetically pleasing.
sean
--
signature.asc
Description: Digital signature
it's due time
to consider splitting it off into another package (someone else already
gave such a suggestion).
sean
signature.asc
Description: Digital signature
ed java sans-package.
i'd consider simply adding a note to README.Debian/NEWS.Debian about
said problem, and being done with it altogether. maybe leave the bug
open at wishlist+wontfix for reference too, i guess.
sean
--
signature.asc
Description: Digital signature
" package.
policy already states that init scripts (9.3.2) and cronjobs (9.5)
must do so, the other stuff is a little more context dependant.
sean
--
signature.asc
Description: Digital signature
t; and the principle of least surprise should apply.
> >
> > We can however change the expectations for new messages being sent to
> > debian-private, and in 3 years *they* would become public by default.
>
> Seconded, on all points, for the same reasons.
Thirded.
sean
--
signature.asc
Description: Digital signature
Package: wnpp
Severity: wishlist
Owner: Sean Finney <[EMAIL PROTECTED]>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(explanation for why there needs to be a nagios2 given after the blurb)
Package name: nagios2
Version : 2.0 (when released)
Upstream Author : Ethan G
done so if i am in fact totally
off-base on my assumptions.
sean
[1] http://bugs.debian.org/340279
[2] http://lists.debian.org/debian-hppa/2005/11/msg00017.html
[3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=342244
[4]
http://buildd.debian.org/fetch.php?&pkg=mysql-dfsg-5.0&am
an't imagine them being at all
practical in what's supposed to be a short, informative description of
a package.
sean
signature.asc
Description: Digital signature
n logically follow that reload must not start a service which is
not running.
is my interpretation of this correct, or am i over-analyzing things?
thanks,
sean
--
signature.asc
Description: Digital signature
er developers, no
matter how justified you feel you may be.
please post follow-ups to -private.
sean
--
signature.asc
Description: Digital signature
is usually not
justification for a grave status. grave is typically reserved for
uninstallable packages (that is, dpkg fails), or bugs involving serious
dataloss/security issues.
sean
--
signature.asc
Description: Digital signature
(policy/fhs)
sean
signature.asc
Description: Digital signature
me. gee, thanks guys!
so this means we need to coordinate another transition, new binary
package names, etc, before we've even finished transitioning to
the previous package. at least it happened before etch was
released...
sean
signature.asc
Description: Digital signature
g be removed on purge?
- should (logrotated) /var/log/foo/foo.log.[0-9]*.gz be removed on purge?
- should /var/log/foo be removed recursively on purge?
i don't remember what the result of the thread was, sorry :(
sean
signature.asc
Description: Digital signature
de functionality, which might make messing with either
of the files moot. i'll have to look more into these details...
> unnecessary in the common case. (I still need some time to read this
> thread about the common database infrastructure *sigh*).
you can get the highlights on my p.d.o page :)
sean
--
signature.asc
Description: Digital signature
on.
> - Has this been resolved?
no, afaik the openssl-related code in debian mysql-foo is disabled[1].
not that i wouldn't mind having it back...
sean
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=291945
--
signature.asc
Description: Digital signature
uot;,
it should stay out of /usr/bin, and go in
/usr/share/gettext-base/scripts or something more appropriate like
that.
looking at the script snippet in question, all it does is set a couple
functions/variables, so it certainly should not be in /usr/bin. hell,
it's not even executable.
but test for a user-environment
variable that could override the default location (though i think
the previous suggestion is less hackish).
sean
--
signature.asc
Description: Digital signature
there are a few unanswered questions,
such as getting it working with module-assistant (which i imagine
is actually in the docs for m-a), and more importantly getting it to
automatically build against all the stock debian kernels.
so, does anyone know of a document that covers this topic?
thank
desktop_owner ()
{
owner_display=$1;
w | awk '{print $1" "$2}' | grep "$owner_display$" | awk '{print $1}'
}
example:
copelandia[~]07:29:50$ get_desktop_owner :0
seanius
i invite someone to invent a better way, i'd like to hear it :
sean finney wrote:
i invite someone to invent a better way, i'd like to hear it :)
Rather than invoke awk twice, just use awk for everything (-:
(I used $DISPLAY for testing)
w | awk "\$3 ~ /$DISPLAY/ {print \$1; exit 0}"
Note the escaped '$'s.
--
To UNSUBSCRIBE, email to
utmpx databases,
called "wuzzah". while the program itself may or may not be helpful for
this specific need, the source code would be helpful if you go this
direction (and are using a c program).
sean
--
signature.asc
Description: Digital signature
Michelle Konzack wrote:
It works in SARGE and SID but not under WOODY because I get only
user/dev/pts/1
well, the 'w' program from procps has not really changed. My woody box
has procps version 2.0.7. So either a) you have an odd version or b) the
utmp data has changed. If b) is the rea
Eduard Bloch wrote:
So I suggest to set a kind of soft policy:
every package maintained by a group should keep a file (with a common
filename) in the Debian diff, which tells all neccessary things:
- who are members of that group
- which person from this group is responsible for exactly this pack
directly credit their work, which i redirect into a file under
/usr/share/doc/$package/ during package build.
if anyone's interested, it's at:
http://people.debian.org/~seanius/goodies/credit-xlators/credit-xlators
sean
--
signature.asc
Description: Digital signature
5 all
in the archive at the same time will lead to not only archive/mirror
bloat (which is considerable by itself), but also probably a very
complicated set of interdepenencies and very frustrating bugs
resulting from said dependencies.
sean
--
signature.asc
Description: Digital signature
is equal to software...
i'm a fan of the academic free license v2, which i think does what the
gfdl meant to do. it allows modifications and redistribution, as long
as the modifications from the original are clearly stated.
sean
--
signature.asc
Description: Digital signature
a mirror (web requests for debian.org w/o the www time out).
sean
--
signature.asc
Description: Digital signature
thank goodness for google caching :)
actually, this brings up something i've been wondering for a bit now:
is there any form of backups in place for any of the debian.org machines?
sean
--
signature.asc
Description: Digital signature
ithout adding yet another useless package to rot in the archives
sean
--
signature.asc
Description: Digital signature
1 - 100 of 1219 matches
Mail list logo
