Ian Jackson wrote:
> Jay Berkenbilt writes ("orphaning psutils"):
>> retitle 777699 O: psutils -- PostScript document handling utilities
>> thanks
>>
>> I'm going to go ahead and orphan these. The RFA has been open for a long
>> time, and the pac
ld of course do so. Otherwise, I suppose
this is ready to be adopted by anyone else who wants to maintain it.
Thanks.
--
Jay Berkenbilt
Ian Jackson wrote:
> Jay Berkenbilt writes ("packages for adoption: icu, tiff, xerces-c, psutils"):
>> The other two packages are relatively low-effort packages to maintain.
>> The psutils package is dead upstream though there is someone out there
>> who mig
s out, but I was not able to get the transition done for
jessie. Now ICU 54 is out, and one of the first jobs of icu's next
maintainer will be, post jessie, to orchestrate a transition of icu to
version 54.1 or whatever is current at the time. This would be a good
way to cut your
ng up vips and nip2 as well. They are very low
effort, and upstream is super-responsive, so I can probably still handle
them even with almost no time, but if you wanted them, I'd be open to
it.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
98
psutils: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777699
--
Jay Berkenbilt
signature.asc
Description: PGP signature
with Unicode 6.3 in ICU
(and ICU4J) for Jessie, but I'd welcome other suggestions.
If someone thinks I'm off base in suggesting that ICU and ICU4J might be
in a different place from other packages that use Unicode data in some
incidental way, feel free to set me straight.
--
Jay Berken
s the experience I had with
tiff.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/20140407141400.0240630403.qww314...@jberkenbilt-linux.appiancorp.com
└── d
3 directories, 1 file
% patmv -w s,/,.,g a/b/c/d
mv a/b/c/d a.b.c.d
Also, since patmv echoes the mv commands that it is running (unless run
with -s), you can also do stuff like
patmv -n s/\./_/g | sed -e 's/^/git /'
to generate git mv commands. I use it this way all
rt.cgi?tag=libtiff4-dev;users=q...@debian.org
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/20140118223748.0400818596.qww314...@soup.q.qbilt.org
ow up with possible NMUs in a few weeks. xerces-c2 is
going to be very hard to support from a security standpoint, and most
programs port to xerces-c without any changes, so it would be great to
be back to having only one xerces-c in the archive for Jessie.
--
Jay Berkenbilt
--
To UNSUBSCRIBE
ould break packages with
versioned dependencies on libtiff5-dev and not provide much more than
aesthetic benefit, so I'm not sure that it's worth it.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
the build dependency.
* If your package build-depends on libtiff5-dev, you don't HAVE to do
anything, but you may be helping yourself in the future if you change
the build dependency to libtiff-dev (>> 4.0.3-6~).
I have replicated most of this information in README.Debian for the t
e...while I'm not much of a python programmer (I did one
decent-sized python project in 1997 or thereabouts), I can see that
there would be no use for a .a file by a python program. I already have
other stuff in my rules file to get rid of some other files that vips
installs that we don&
ge, or whether this is a new bug, or whether this
is a difference because of fewer python versions being available or
what.
Thanks. This is blocking me from uploading a new version of vips.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of &qu
Russ Allbery wrote:
> Jay Berkenbilt writes:
>> Ondřej Surý wrote:
>
>>> This results in:
>>>
>>> E: libgd-tools: binary-or-shlib-defines-rpath usr/bin/annotate
>>> /usr/lib/x86_64-linux-gnu/libtiff5-alt
>
>> Yes, I'm afraid that&#
ll have to use a lintian override. Here's
mine from the vips package:
# This is temporary until libtiff5-alt-dev goes away.
libvips31: binary-or-shlib-defines-rpath
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe"
of gd to switch from libtiff5-dev to
libtiff5-alt-dev until the tiff transition.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/20130520141454.0240755266.qww314...@jberkenbilt-linux.appiancorp.com
requires tiff 4.x.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/20130520141303.0240764509.qww314...@jberkenbilt-linux.appiancorp.com
n exactly the way I'm thinking it will.
For additional details, see my message to the release team:
http://lists.debian.org/debian-release/2013/05/msg00127.html
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Troubl
n supporting both for some time. If you run into compile errors, you
can either explicitly build depend on libtiff4-dev and nag your
upstream, or you can fix them yourselves based on the information here:
http://libtiff.maptools.org/v4.0.0.html
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to d
Goswin von Brederlow wrote:
> Sven Joachim writes:
>
>> On 2012-03-24 10:50 +0100, Adam Borowski wrote:
>>
>>> On Sat, Mar 24, 2012 at 09:48:58AM +0100, Sven Joachim wrote:
>>>> On 2012-03-24 04:04 +0100, Jay Berkenbilt wrote:
>>>> > One i
I'm
not sure whether a precedent or convention has been established.
Thanks.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://l
Please reply to me directly (or CC me on replies) as I am not currently
subscribed to debian-devel.
Enrico Weigelt wrote:
> * Jay Berkenbilt schrieb:
>> I'm looking for someone who might like to take over the icu package.
>> This is ICU4C (C/C++), not to be confused with IC
Please reply to me directly (or CC me on replies) as I am not
currently subscribed to debian-devel.
Enrico Weigelt wrote:
> * Jay Berkenbilt schrieb:
>>
>> I'm looking for someone who might like to take over the icu package.
>> This is ICU4C (C/C++), not to be
possible. Thanks.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110529084644.3019965905.qww314159@soup
I'd probably give preference to the debian SGML/XML group or
to other groups maintaining stuff from apache.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
s a
flurry of activity dealing with backporting security fixes or fixing
obscure problems. Many times problems have been found in pre-release
versions, so I highly recommend packaging those in experimental and
encouraging people to try them out. In this way, we have had very few
problems with serious pro
ole
PDF documents themselves, not making use of PDF security.
It is very easy to defeat PDF security in any file that has a blank user
password since it is just up to the application to enforce security.
I've written a detailed explanation of this which I can dig up and send
you if you're i
t hear any problems, I'm going to coordinate with the release team
to get ICU 4.4 into squeeze. I've already tested the xerces packages,
and they are fine with the new ICU. Thanks!
--
Jay Berkenbilt
pgppMEXhW8vkr.pgp
Description: PGP signature
I've uploaded ICU 4.3.4 to experimental. Soon this will be ICU 4.4. If
you maintain a package that depends on ICU, it would be great if you
could test against this release.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "u
hared library runtime packages install as
libtiff5, so they can coexist with the versions in sid/squeeze. The
development package, libtiff-dev, conflicts with libtiff4-dev from
sid/squeeze.
Thanks!
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a su
Never mind about trying the new libtiff4 in experimental. The response
from upstream to my statement that I was putting the head of the 3-9
branch in debian was to agree that it was ready to release and to
release 3.9.0. :-)
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-devel-requ
4 package and
install it. Everything should "just work". Thanks.
--
Jay Berkenbilt
pgpXOB0Tum5ti.pgp
Description: PGP signature
.html#Migrateto300
I will eventually be requesting that the xerces 2 packages be classified
as "oldlibs" or maybe removed entirely. I anticipate not requesting
removal until squeeze+1, but we'll see how it goes.
Thanks!
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email
my chroot and not updated my regular
system. Or maybe I got caught in a window with my local mirror. Oh
well. Time to clean and reconnect my brain cables.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
r I'm doing something
wrong in my rules. All I do in my rules is
include /usr/share/cdbs/1/rules/debhelper.mk
and I have one .doc-base file.
Once I know where the problem is, I can either fix my packages or
submit a bug to the appropriate place.
--
Jay Berkenbilt
--
To UNSUBSCRIBE
n-issue, and I can use the upstream source
download as the .orig.tar.gz file.
Thanks for all the input and tips.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
, I'll just
continue to use tarball in tarball and will wait to restructure my
packages until after we can switch to 3.0 (quilt).
I'm going to try to make a decision soon since I have a new upstream
version of ICU ready to upload to experimental as soon as I resolve
this. Thanks.
--
Package: wnpp
Severity: wishlist
Owner: Jay Berkenbilt <[EMAIL PROTECTED]>
* Package name: qpdf
Version : 2.0
Upstream Author : Jay Berkenbilt <[EMAIL PROTECTED]>
* URL : http://qpdf.sourceforge.net/
* License : Artistic License Version 2.0
Prog
libxml-xerces-perl. I'll
have to test this scheme carefully to make sure it works, but I think
it will work fine.
Comments?
--
Jay Berkenbilt <[EMAIL PROTECTED]>
pgpXg9YM8sWdm.pgp
Description: PGP signature
. I'll report bugs to any
depending packages that have not uploaded a new version within several
days of the upload. I'll send another message out when I upload (but
I will not copy debian-devel on that one).
--
Jay Berkenbilt <[EMAIL PROTECTED]>
pgpzjY6Rg0fnm.pgp
Description: PGP signature
he missing
prerequisites on pergolesi in the appropriate chroot.
Thanks for any suggestions.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Mike Hommey <[EMAIL PROTECTED]> wrote:
> On Sat, Oct 13, 2007 at 12:36:04PM -0400, Jay Berkenbilt wrote:
>> So, what am I missing? How do I get access to an amd64 system to fix
>> this problem?
>
> try the sid_amd64_pure chroot ;)
Thanks! Okay, now how was I
virtual
power management: ts ttp
So, what am I missing? How do I get access to an amd64 system to fix
this problem?
If anyone is interested, please look at bug 446276.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe
it tends to happen that some
particularly tightly integrated packages like libxml-xerces-perl and
xalan only work properly with one specific version of xerces. It is
my intention to request removal of xerces27 before lenny releases if
at all possible.
--
Jay Berkenbilt <[EMAIL PROTEC
h a vested
interest to give these a spin especially with upstream primed to
include fixes before the 3.8 release in September.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
pgpEA63htKiHm.pgp
Description: PGP signature
oping (if the release team approves) to be
able to get ICU 3.6 into etch. Thanks.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
pgpKKTltMsuan.pgp
Description: PGP signature
non-compatible changes to the protocol. I have
a version ready to upload to backports.org which I will upload as soon
as 3.9.0 hits testing. In the mean time, if you use dxpc, please be
aware that the next upload will break compatibility with dxpc running
on older systems.
--
Jay Berkenbilt
Package: wnpp
Severity: wishlist
Owner: Jay Berkenbilt <[EMAIL PROTECTED]>
* Package name: diff1
Version : 0.4.1
Upstream Author : April Furst
* URL : http://www.diff1.net/
* License : GPL, `diff1 -u GFDL | patch`
Description : compares file&#x
message from subversion, the first thing I do is check for
typos, and the second thing I do is check to make sure all
prerequisites for whatever I'm trying to do have been satisfied. That
might have caused you to notice the missing mkdir between your two svn
mv commands. Just my $0.02.
message from subversion, the first thing I do is check for
typos, and the second thing I do is check to make sure all
prerequisites for whatever I'm trying to do have been satisfied. That
might have caused you to notice the missing mkdir between your two svn
mv commands. Just my $0.02.
free to contact me off list if you
look at this and have any questions about how it works. The basic
approach I used was to create two symlink farms to the extracted
sources and build once in each location.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL P
eveloper community than the complaints of an irate user.
It's also worth noting that constructive comments or actual help have
a stronger track record of improving things than do sarcastic
remarks. Either way, the original subject of the message was right on
target!
--
Jay Berkenbilt <[
Thomas Viehmann <[EMAIL PROTECTED]> wrote:
> Hello Jay,
>
> Jay Berkenbilt wrote:
>> My inclination would be decline requests to add unrelated packages to
>> psutils, but I thought I'd solicit input from others in case someone
>> has some perl (oops, p
sean finney <[EMAIL PROTECTED]> wrote:
> hi jay,
>
> On Sat, Nov 19, 2005 at 12:27:33PM -0500, Jay Berkenbilt wrote:
>> I'm not sure that, as an upstream author, I would necessarily want
>> the debian version of my package to be bundled with other software
>>
pearl) of wisdom that I have overlooked. Thanks!
--
Jay Berkenbilt <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ixing
the underlying problem as many suggested.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
pt script written by Michael Dänzer
posted to bug 192008 (which I saw after writing all of the above) that
could be a good starting place if this is actually worth pursuing.
Comments? If there's no consensus, I'll probably abandon this project
and just use a script to help me do it by hand when I need to do this.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
Rob Browning <[EMAIL PROTECTED]> wrote:
> Jay Berkenbilt <[EMAIL PROTECTED]> writes:
>
>> I use these and would be happy to adopt the package.
>
> OK, that sounds good, and thanks. I just uploaded 1.17-19 which seems
> to be doing fine with the autobuilders.
Sou
I use these and would be happy to adopt the package.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Steve Langasek <[EMAIL PROTECTED]> wrote:
> On Mon, Sep 19, 2005 at 04:45:31PM -0400, Jay Berkenbilt wrote:
>
>> Though grep-excuses shows them to be valid candidates, both icu and
>> vips appear to be not transitioning to testing because of making
>> packages uninst
ave
I overlooked something? I don't see why these transitions should
happen on their own. Thanks for any resolution or explanation.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
e looked (other than reading the
code to buildd and/or wanna-build) to find the exact method used to
calculate the build order?
--
Jay Berkenbilt <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
y can get fixed while the changes are fresh. The first thing
I did was look for a pseudopackage in the bug tracking system for PTS,
but I couldn't find one. Perhaps I overlooked it?
Thanks!
--
Jay Berkenbilt <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
d be more robust.
Besides, based on popularity contest, no one is really using the
features of the old packaging that would allow certain very advanced
customizations to be made after installation. It's also worth noting
that blade's icu28 packages use the shared-library data packagi
ekend?
An alternative would to resolve the FTBFS on arm for icu 2.1 (which
worked before g++ 4.0) and to wait for xerces25 to rebuild and then to
do a binary NMU rebuild of libxml-xerces-perl
Thoughts?
--Jay
--
Jay Berkenbilt <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
w
even more unusually busy than their usual
level of unusualness right now in both my personal and professional
lives...) Of course, all ideas and suggestions such as this are
welcome and are being saved in my notes, in spite of any first
impressions I may have on whether they will actually work
s
lear to me what a fixed libtool would do differently (I don't
know libtool that well) though. Anyway, I've been looking for an
excuse to dig into this. Once I could clearly articulate why libtool
is broken and what a non-broken libtool would look like, it will be
much clearer what k
Steve Langasek <[EMAIL PROTECTED]> wrote:
> - Leave the .la files in place; -dev packages need to depend on -dev
> packages corresponding to those runtime dependencies that are also built
> using libtool. This is the status quo.
If we do this (which I think we should for now), I would sugges
turn around and immediately upload to
unstable. (See tiff for an example.) Do you happen to know whether
this procedure makes a difference? (I realize, of course, that
generating information from the package list in NEW does not imply
knowledge of the order in which ftp-masters approve or reject
p
h the original to make sure that your patch and the original
patch set produce the same result.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
27;ve really missed something here), I'd like to proceed with my
original plan. Is that okay?
I really appreciate the responses to this. I feel like I'm making a
lot of noise over a few packages that are not that important over an
issue that isn't that major. All this input is hel
Colin Watson <[EMAIL PROTECTED]> writes:
> On Mon, Jan 17, 2005 at 03:53:58PM +0100, Santiago Vila wrote:
>> On Tue, 18 Jan 2005, Anthony Towns wrote:
>> > We really need to get dpkg/apt and dselect/aptitude working as designed.
>> > Not supporting auto-selecting packages like this, in spite of
uld really know about. If I had made
explicit mention, someone might scratch their head and say, "Why is he
repeating mention of previously noted changes?"
I'm walking away from this discussion with the impression that I
handled the changlog for tiff correctly. If I should walk awa
Anthony Towns wrote:
> Jay Berkenbilt wrote:
>> The recent threads on sonames and package names convinced me beyond a
>> doubt that I made a mistake in the names of the vips packages.
>
> Oh dear...
>
>> [...] Right now, the vips7.10 source package creates four b
and apt-get upgrade/dist-upgrade are
happy to upgrade a package whose architecture status has changed. I
just want to double check to avoid an unnecessary delay in planning a
package transition. Thanks!
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
--
To UNSUBSCRIBE, email t
ompelling reason not to. :-)
In the interest of full disclosure, in the original ITP, David Moreno
Garza <[EMAIL PROTECTED]> asked why I was including the version number
in the package name and I gave a reason. In retrospect, the reason
wasn't really valid.
Thanks!
--
Jay Berken
Jeroen van Wolffelaar <[EMAIL PROTECTED]> writes:
> On Wed, Jan 12, 2005 at 01:01:34PM -0500, Jay Berkenbilt wrote:
>> ... or put an entry in the latest changelog block with a parenthetical
>> remark saying that bug was actually fixed by version x.y-z.
>
> I'v
uldn't rely on someone having done
that. Anyway, changes to stable are definitely in a different
category from changes to unstable
My opinions should, of course, not be construed as "consensus" since
I'm definitely a newcomer. I consider them worth posting though
because they came partially from a discussion on IRC that involved
people of greater experience. :-)
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
te/helpful things those of us waiting on
[EMAIL PROTECTED] can do to help speed the process? I've even
resorted to sending email to the individual buildd admins, but this
has also always failed, even though I try my best to be pleasant about
it.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
it works well for you.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
client class of UXTerm and a
client name of xterm. Maybe this is debian-specific? I thought only
uxterm did that.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
in some modes. I have used dvd+rw-tools for some
time as my exclusive software for DVD authoring, even on dvd-r and
dvd-rw. Also, cdrdao has some CD writing capability (not withstanding
caveats and warnings in README.Debian) and is not, to my knowledge,
related to cdrtools.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
84 matches
Mail list logo
