ted in hearing thoughts from other people who
have converted an rpm-based infrastructure to a dpkg-based
infrastructure.
Lastly, please feel free to correct my terminology if I'm using it
incorrectly. For example, is it correct to say dpkg-based rather than
deb-based?
Thanks!
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
simple that someone
with the inclination should be able to decide to do an NMU with very
little time or effort. If you're willing to sponsor me as a
comaintainer of the packages, I'd like to know that too. We would, of
course, have to coordinate with Ivo. Thanks for your time.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
> Jay Berkenbilt <[EMAIL PROTECTED]> writes:
> > I am interested in possibly co-maintaining the xerces packages or in
> > taking them over. Ivo Timmermans, the current maintainer of the
> > xerces packages, indicated on [1]debian-devel that he is "lookin
ML
> group.
>
> If you want your welcome to join the group.
Thanks. I'll definitely check this out. Someone kindly volunteered
to look over my packages. Should I still move forward with the NMU?
I just need to redo the packages following the proper policy for NMU
which I didn&#x
rge?
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=219151
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
nd the Debian revision is 1. I thought I'd
mention this so that it was clear that I did it this way on purpose.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
> > I'd like to request a sponsor for my "patmv" package. patmv is a Perl
> > script that can be used to do bulk renames on files based on a Perl
> > expression ("pattern"). I've been using this script for about 10
> > years, and it has a small following among current and former
> > co
) and serves a different cross section of the
Debian user community.
> I might be willing to sponsor it; let me think about it a bit.
I appreciate your consideration. So that I don't have to come across
as nagging, can you give me some kind of timeframe within which you
expect to respond?
> Jay Berkenbilt wrote:
> > Although I failed to mention this in my initial post, the thing that
> > pushed me over the edge and made me decide to submit this package for
> > sponsorship was the recent inclusion of the "renameutils" package,
> >
be its own package.
I hope that this email is taken in the positive and respectful spirit
with which it is intended. Any forcefulness in my language should be
interpreted only as an indication of the strength of my conviction on
this point. I truly appreciate the suggestions and the implicati
that may or may not coexist peacefully with other
packages), I completely acknowledge that patmv is not something anyone
will come looking for.
Thanks again for the responses and interest!
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
somewhere, a
pointer would be appreciated. The apt.conf and debconf-devel
documentation have lots of hints, but nothing that looks easier than
the approach I'm planning on trying.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
ed release-critical bugs against console-common. I'll post
my solution to debian-devel today with the subject "testing
config/preinst mods: one approach".
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
lot,
> Fabio.
As a point of comparison, I'm helping with maintenance of the xerces
packages and had xerces25 (new) uploaded by a sponsor. The package
was initially uploaded on May 4 and appeared in unstable on May 18.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
ssh, pcmcia,
> hotplug and networking. Thus allowing acces to the "hanging" machine
> even with pcmcia network cards.
This is true only as long as DELAYLOGIN=no in /etc/default/rcS or
rmnologin is moved earlier as well.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
, explaining the potential security risks,
and have the default be "no". You can look at man-db
(dpkg-reconfigure man-db) for example of how you might want to word
this.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
It just keeps getting better.
It also was the tool that introduced me to wxWidgets
(f.k.a. wxWindows) which I use for my own GUI development now.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
"Check why" there to
see the reasons.
http://bjorn.haxx.se/debian/testing.pl?package=cvs2svn
You'll see that this is blocked by subversion which in turn is blocked
by perl. Lots of things are blocked by perl, but there appears to be
active effort in resolving that issue.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
mmand-line tools in one source package that creates four binary
packages (runtime, dev, doc, and tools) and then a separate graphical
front end that depends on the runtime and build-depends on the dev.
I'll be posting an RFS for these packages probably within the next day
or so.
--
Jay
> If B fails to build from source, is it
> > the case that manual intervention is then required to get it to retry,
> > or does this happen automatically? Thanks again for any
> > clarification.
>
> That depends on the reason of not-building. What reasons
software will take a look at these. I don't want
to seem impatient, which is why I mention this up front. I'm only
trying to act quickly because of the looming sarge freeze. :-)
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
s, I will ask two people who have sponsored
uploads for me before, but I'm hoping someone who is interested in
image manipulation software will take a look at these. I don't want
to seem impatient, which is why I mention this up front. I'm only
trying to act quickly because of the looming
n arm and upload them before the freeze?
* In xerces23 and xerces24, other architectures out of date, but
their buildd logs show success. Why would they be out of date if
they were built successfully? What can I do to resolve this?
Thanks for any clarification.
--
Jay Berkenbilt &l
> > * On all three packages, the arm build failed because of an
> >unsatisfiable build dependency that was the result of a timing
> >problem. These should succeed now as the problem with the
> >dependent package has been cleared. I emailed
> >[EMAIL PROTECTED] to reque
> > Yes, it seems the most recent arm build failed, but yet the current
> > icu28 (2.8-3) is in testing. Perhaps someone built it manually.
> > There are no bugs posted again icu28.
>
> In testing but not in unstable for arm? Or in testing without arm
> support?
Hmm. In testing and un
> > http://people.debian.org/~wouter/wanna-build-states
>
> There's a lot of information hidden beneath the surface, it seems. Is
> there a place through which I could have discovered this, other than
> asking on debian-mentors? :-)
Answering my own question, I see a link to this in bu
>I was writing to Ivo Timmermans[1] that I would like to continue with some
> of his packages, as he has not updated them for a while. They are music
> players (mean: binary, libs) for C64 music formats, ie: SID emulator.
> He said it is OK for him, but when I have updated the packages,
ackages because someone has agreed to
sponsor them for upload into the archive, and I want to tweak the
description from what's there on mentors.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
?
Most people will have all those libraries on their systems anyway, and
I suspect not many people running systems without X will bother with
libtiff-tools.
Thanks for any advice.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
f tiffgt.1.gz. Since
Replaces will appear without Conflicts, libtiff-tools won't get
removed. When it gets upgraded, tiffgt.1.gz will not be removed.
Once libtiff-opengl is installed, it will no longer be possible to
install an older version of libtiff-tools, but I don't consider tha
ed release-critical bugs against console-common. I'll post
my solution to debian-devel today with the subject "testing
config/preinst mods: one approach".
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
somewhere, a
pointer would be appreciated. The apt.conf and debconf-devel
documentation have lots of hints, but nothing that looks easier than
the approach I'm planning on trying.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
nd the Debian revision is 1. I thought I'd
mention this so that it was clear that I did it this way on purpose.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> > I'd like to request a sponsor for my "patmv" package. patmv is a Perl
> > script that can be used to do bulk renames on files based on a Perl
> > expression ("pattern"). I've been using this script for about 10
> > years, and it has a small following among current and former
> > co
) and serves a different cross section of the
Debian user community.
> I might be willing to sponsor it; let me think about it a bit.
I appreciate your consideration. So that I don't have to come across
as nagging, can you give me some kind of timeframe within which you
expect to respond?
> Jay Berkenbilt wrote:
> > Although I failed to mention this in my initial post, the thing that
> > pushed me over the edge and made me decide to submit this package for
> > sponsorship was the recent inclusion of the "renameutils" package,
> >
be its own package.
I hope that this email is taken in the positive and respectful spirit
with which it is intended. Any forcefulness in my language should be
interpreted only as an indication of the strength of my conviction on
this point. I truly appreciate the suggestions and the implicati
that may or may not coexist peacefully with other
packages), I completely acknowledge that patmv is not something anyone
will come looking for.
Thanks again for the responses and interest!
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
--
To UNSUBSCRIBE, email to [EMAIL PRO
lot,
> Fabio.
As a point of comparison, I'm helping with maintenance of the xerces
packages and had xerces25 (new) uploaded by a sponsor. The package
was initially uploaded on May 4 and appeared in unstable on May 18.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org
ssh, pcmcia,
> hotplug and networking. Thus allowing acces to the "hanging" machine
> even with pcmcia network cards.
This is true only as long as DELAYLOGIN=no in /etc/default/rcS or
rmnologin is moved earlier as well.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.q
, explaining the potential security risks,
and have the default be "no". You can look at man-db
(dpkg-reconfigure man-db) for example of how you might want to word
this.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
It just keeps getting better.
It also was the tool that introduced me to wxWidgets
(f.k.a. wxWindows) which I use for my own GUI development now.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
"Check why" there to
see the reasons.
http://bjorn.haxx.se/debian/testing.pl?package=cvs2svn
You'll see that this is blocked by subversion which in turn is blocked
by perl. Lots of things are blocked by perl, but there appears to be
active effort in resolving that issue.
--
Jay Berk
mmand-line tools in one source package that creates four binary
packages (runtime, dev, doc, and tools) and then a separate graphical
front end that depends on the runtime and build-depends on the dev.
I'll be posting an RFS for these packages probably within the next day
or so.
--
Jay
> If B fails to build from source, is it
> > the case that manual intervention is then required to get it to retry,
> > or does this happen automatically? Thanks again for any
> > clarification.
>
> That depends on the reason of not-building. What reasons
software will take a look at these. I don't want
to seem impatient, which is why I mention this up front. I'm only
trying to act quickly because of the looming sarge freeze. :-)
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
--
To UNSUBSCRIBE, email to [EMAIL
n arm and upload them before the freeze?
* In xerces23 and xerces24, other architectures out of date, but
their buildd logs show success. Why would they be out of date if
they were built successfully? What can I do to resolve this?
Thanks for any clarification.
--
Jay Berkenbilt &l
> > * On all three packages, the arm build failed because of an
> >unsatisfiable build dependency that was the result of a timing
> >problem. These should succeed now as the problem with the
> >dependent package has been cleared. I emailed
> >[EMAIL PROTECTED] to reque
> > Yes, it seems the most recent arm build failed, but yet the current
> > icu28 (2.8-3) is in testing. Perhaps someone built it manually.
> > There are no bugs posted again icu28.
>
> In testing but not in unstable for arm? Or in testing without arm
> support?
Hmm. In testing and un
> > http://people.debian.org/~wouter/wanna-build-states
>
> There's a lot of information hidden beneath the surface, it seems. Is
> there a place through which I could have discovered this, other than
> asking on debian-mentors? :-)
Answering my own question, I see a link to this in bu
>I was writing to Ivo Timmermans[1] that I would like to continue with some
> of his packages, as he has not updated them for a while. They are music
> players (mean: binary, libs) for C64 music formats, ie: SID emulator.
> He said it is OK for him, but when I have updated the packages,
ackages because someone has agreed to
sponsor them for upload into the archive, and I want to tweak the
description from what's there on mentors.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubs
?
Most people will have all those libraries on their systems anyway, and
I suspect not many people running systems without X will bother with
libtiff-tools.
Thanks for any advice.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
w
f tiffgt.1.gz. Since
Replaces will appear without Conflicts, libtiff-tools won't get
removed. When it gets upgraded, tiffgt.1.gz will not be removed.
Once libtiff-opengl is installed, it will no longer be possible to
install an older version of libtiff-tools, but I don't consider tha
ackages and would
then request removal of the old packages by posting a bug against
ftp.debian.org.
Advice welcome and appreciated. Thanks.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Jay Berkenbilt <[EMAIL PROTECTED]> writes:
> The recent thread on names of library packages on debian-devel made me
> decide that I made a mistake in naming one of my packages.
> Specifically, the vips7.10 source package creates four binary
> packages: libvips7.10, libvips7.1
Santiago Vila <[EMAIL PROTECTED]> writes:
> On Fri, 14 Jan 2005, Jay Berkenbilt wrote:
>
>> I've read Section 5.9.3 of the developer's reference and understand it
>> clearly. Is that still the best way to go?
>
> Not always, unfortunately. Very often, t
client package. Again, this problem could happen only
under a short window of time, and would only happen if someone
explicitly tried to install the new package, not if someone did a
dist-upgrade. I think this kind of thing happens all the time.
Well, this is long, but maybe it will help som
. In other words, you could include a malicious
link or put invalid PDF data that would exploit a security hole in a
specific PDF viewer, but you can't actually embed malicious code.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
Alejandro Exojo <[EMAIL PROTECTED]> wrote:
> El Viernes, 11 de Febrero de 2005 17:21, Jay Berkenbilt escribiÃ:
>> That isn't to say that it is impossible to create a security hole
>> through a PDF file, but it's more comparable to html in that respect
>> tha
t who mentioned that your
writing is clear and informative. When I was just getting started,
this was one of the most helpful things I read.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ted in hearing thoughts from other people who
have converted an rpm-based infrastructure to a dpkg-based
infrastructure.
Lastly, please feel free to correct my terminology if I'm using it
incorrectly. For example, is it correct to say dpkg-based rather than
deb-based?
Thanks!
--
Jay Berke
simple that someone
with the inclination should be able to decide to do an NMU with very
little time or effort. If you're willing to sponsor me as a
comaintainer of the packages, I'd like to know that too. We would, of
course, have to coordinate with Ivo. Thanks for your time.
--
Jay Be
> Jay Berkenbilt <[EMAIL PROTECTED]> writes:
> > I am interested in possibly co-maintaining the xerces packages or in
> > taking them over. Ivo Timmermans, the current maintainer of the
> > xerces packages, indicated on [1]debian-devel that he is "lookin
ML
> group.
>
> If you want your welcome to join the group.
Thanks. I'll definitely check this out. Someone kindly volunteered
to look over my packages. Should I still move forward with the NMU?
I just need to redo the packages following the proper policy for NMU
which I didn&#x
rge?
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=219151
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
66 matches
Mail list logo
