Package: libcinnamon-menu-3-0
Version: 4.8.2-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Upgraded libcinnamon-menu-3-0 and gir1.2-cmenu-3.0 4.6.1-1->4
reassign 944995 ftp.debian.org
thanks
Please remove gtkimageview from unstable. There is no gtk3
version. Upstream is dead. I can't find any reverse dependencies.
It has a popcon vote+old+recent score of 42.
signature.asc
Description: OpenPGP digital signature
On 26/11/17 16:08, Damyan Ivanov wrote:
> [added maintainer of gscan2pdf to CC. gscan2pdf is the only reverse
> dependency of libgoo-canvas-perl]
>
> goocanvas is deprecated & replaced by goocanvas-2.0. gscan2pdf depends
> on libgoo-canvas-perl, which uses goocanvas.
>
> Are there any plans to m
Package: netgen
Version: 4.9.13.dfsg-8+b3
Severity: grave
Justification: renders package unusable
$ netgen
NETGEN-4.9.13
Developed at RWTH Aachen University, Germany
and Johannes Kepler University Linz, Austria
Including OpenCascade geometry kernel
Parsing ng.tcl
optfile ./ng.opt does not exist -
On 29 July 2012 04:11, John Goerzen wrote:
> One more bug: I have to manually change the backend from libsane-perl to
> scanimage-perl each time I run it. My preference no longer saves, and
That's not a bug - it's a feature. I wrote scanimage-perl as a way of
debugging the libsane-perl module by
On 19 July 2012 17:53, Evgeni Golov wrote:
> From this I think cuneiform can be perfectly moved to Suggests.
I hadn't realised that cuneiform was non-free.
I don't understand why
Recommends: gocr, tesseract-ocr, cuneiform
is not ok. but
Recommends: gocr | tesseract-ocr | cuneiform
is.
Shoul
clone 678911 -1
severity -1 normal
retitle -1 profiles not working
thanks
> That did fix that one, though my presents still aren't working (even
> if I resave a new one) -- a much smaller problem, for sure. For
> instance, if I set threshold and save a preset, then select that
> preset, the thres
On 14 May 2012 22:48, Willi Mann wrote:
>> I am in half a mind to disable the tests and then deal with any
>> bug reports from the problematic archectures. At least there then
>> might be a user on a suitable machine and motivated to help.
>
> At least for the wheezy release, this sounds like a sa
It is certainly doable, but my first problem is that I have not
managed to reproduce the issue.
If I could get access to a machine which reliably reproduced the
problem, it would certainly be quicker to add some print statements to
the .xs to work out what was going on rather than spend time on
po
Does anyone have any objections to fixing this by uploaded 0.4.4 from
experimental to unstable?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
You seem to be distinguishing between functions declared as inline,
and those inlined by the compiler. My understanding that the compiler
was under no obligation to follow the inline directive, and I don't
see an easy way to check when functions have been inlined or not.
Taking an example - this s
I've attached the build log.
iulib_0.4.4+ds-2_i386.build
Description: Binary data
On 1 April 2012 22:34, Jakub Wilk wrote:
>> The suggested patch indeed fixes the problem. However, the symbols
>> exported are now updated.
>
> What do you mean?
I get a diff that starts like this, and carries on for a couple of
hundred lines:
dpkg-gensymbols: warning: some new symbols appeared
The suggested patch indeed fixes the problem. However, the symbols
exported are now updated. I assume this means that the SONAME should
be bumped.
To what? 0e? How was 0d chosen? d for debian?
The packaging for ocropus should then be updated to fix the dependency
on libiulib0d.
--
To UNSUBSCR
On 26 February 2012 00:44, Jeffrey Ratcliffe wrote:
> I'm trying to debug the FTBFS of libsane-perl on kfreebsd-amd64[1].
>
> I've KiBi was kind enough to install the build-depends on asdfasdf,
> but I can't reproduce the problem - it builds fine.
>
> Does a
I'm trying to debug the FTBFS of libsane-perl on kfreebsd-amd64[1].
I've KiBi was kind enough to install the build-depends on asdfasdf,
but I can't reproduce the problem - it builds fine.
Does anyone have any clue what might be causing the FTBFS on
the kfreebsd-amd64 (and mips, and occasionally s
On 15 February 2012 16:35, Salvatore Bonaccorso wrote:
> I just uploaded libsane-perl 0.04-1 to the archive. And it builded now
> fine on sparc.
Thanks for this.
> *But*: Trying to build the package on smetana.d.o still, sometimes the
> tests hang. I'm not sure if we should downgrade severity he
On 23 July 2011 22:42, Jonathan Wiltshire wrote:
> I'm tying up loose ends and this bug is still outstanding for Squeeze. Do
> you have plans for an upload and would you like any help?
I apologise for not revisiting this in any sane length of time. All of
my (little) time has been taken up with g
Or am I being slow, and this is just because of the Perl 5.12
transition (that being the only change)?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
I see you are building against libsane 1.0.22-2. Were the previous
successful builds against libsane 1.0.22-2, or another?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On 22 March 2011 22:42, Adam D. Barratt wrote:
> Any news on either of the uploads?
Apologies for the delay. RL is throwing up some issues which are
taking my time at the moment. I hope to get to it at the weekend.
Regards
Jeff
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian
On 6 March 2011 23:56, Jakub Wilk wrote:
> Adam is correct, I bumped b-d to shut up lintian:
Thanks for confirming that.
Jeff
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hi Adam,
On 6 March 2011 00:18, Adam D. Barratt wrote:
> - Testing and unstable have tesseract 2.04-2.1, so the package for
> stable would need to have a lower version than that. I'd suggest 2.04-2
> +squeeze1, which is conventional.
Sure. This will be my first contribution directly to stable o
Attached are debdiffs to fix #612032 for the relevant packages in
lenny and squeeze.
Are you happy for these to be uploaded to stable/oldstable?
Would you like separate bugs to be opened for each distribution? At
the moment, the same sid/wheezy bug is quoted/closed.
Regards
Jeff Ratcliffe
tes
> I've prepared an NMU for tesseract (versioned as 2.04-2.1) and uploaded it
> to DELAYED/5. Please feel free to tell me if I should delay it longer.
Upload it immediately, if you wish. Thanks for preparing it.
> This xterm-based debug window feature looked very awkward to me, is
> undocumented a
On 30 July 2010 07:22, Salvatore Bonaccorso
wrote:
> I wonder, when we uploaded 1.230 I had checked as part, some of the
> patches applied, and dropped these:
>
> * debian/patches:
> - Drop gtktreeview_expand.patch applied upstream.
> - t/GtkPrintSettings.t fixed upstream, drop
> gtkpr
On 28 July 2010 00:42, gregor herrmann wrote:
>> If no one objects, then I will prepare them for upload.
I've done this now. I spent the best part of a day scratching my head
over how best to deal with the manpage-has-bad-whatis-entry lintian
warnings for the manpages whose PODs don't correspond
On 27 July 2010 22:18, Ansgar Burchardt wrote:
> But versioning seems to follow a scheme: 1.2xy is unstable if and only
> if x is odd. That should be something we can filter on. We should make
> sure upstream really uses this system before though.
Well spotted! Thanks. This is true.
http://sf.
On 27 July 2010 19:31, gregor herrmann wrote:
>> I'll talk to upstream about maybe rearranging things so that the tools
>> can distinguish between unstable and stable.
>
> Cool, thanks!
> Let's wait for the outcome before making any further decisions, ok?
Looking further, I see the download page
On 27 July 2010 16:18, gregor herrmann wrote:
> What make me a bit unhappy about that is uscan will again show us
> 1.230 if they are in the same directory (and use the same
> filename/versioning scheme).
I'll talk to upstream about maybe rearranging things so that the tools
can distinguish betwe
Upstream thinks that it is a new problem with Gtk2/Glib 1.230:
http://mail.gnome.org/archives/gtk-perl-list/2010-July/msg00012.html
At the moment, there is no patch.
I'll test the new stable branches, but I assume they are unaffected,
so I suggest that we upload these. We would have to bump the
This looks a great deal like
https://bugzilla.gnome.org/show_bug.cgi?id=549138
But I'm not sure why we suddenly seeing a problem spotted 2 years ago now.
I also don't understand why we have the unstable branch of Gtk2-Perl
packaged. Surely we should have Gtk2 1.222 and Glib 1.223, which are
the
retitle 590453 libgtk2-perl: Gtk2::Dialog and descendents signal
produces different response to ->run()
thanks
as per attached script
dialog.pl
Description: Binary data
severity 590453 serious
block 589796 by 590453
thanks
I've made 590453 serious because 589796 is grave.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On 26 July 2010 09:05, Jeffrey Ratcliffe wrote:
> I'll install the relevant packages from sid and see why...
It is the Perl bindings for GTK that are the problem. I'll work up a
patch, or if necessary a test case and submit the appropriate bugs.
In the mean time, if you downgrade
On 25 July 2010 23:53, A. Costa wrote:
> Scanned a blank page, tried to save as a .PDF and quit. The log
> is attached.
Thanks for this. It seems the problem is related to GTK2 or the Perl
bindings - the file browser should return 'ok' or 'cancel' on
selecting the filename, but:
DEBUG - PDF sav
The logging system was previously just print and warn calls. I've now
replaced all that using Log::Log4perl and added a couple of command
line options to support it. I've uploaded a .deb to
http://launchpadlibrarian.net/52500599/gscan2pdf_0.9.32~1_all.deb
There are no other significant changes, ap
On 24 July 2010 15:19, Christopher <608...@bugs.launchpad.net> wrote:
> Please let me know exactly how to apply patches, as i haven't yet
sudo patch /usr/bin/gscan2pdf < debug.patch
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Co
On 24 July 2010 16:14, martin f krafft wrote:
> Importing does not work either, here is the output:
>
> Importing /tmp/zweizeiler.pdf
> Format Portable Document Format
> Creator: TeX
> Producer: pdfTeX-1.40.10
Although assuming this was a two-liner from pdfTex, it probably didn't
Apologies for crossposting the gscan2pdf-help list, Debian, and Ubuntu
bugs, but it makes no sense to have the same conversation three times.
I've installed the main dependencies from sid and still can't reproduce this.
Does it make a difference if the image is imported or scanned?
Please apply
On 22 July 2010 09:03, Nephila wrote:
> Same problem here. I just updated to 0.9.31-1, but still i I can only save in
> gif, jpeg, png and pnm formats. PDF does not work with any compression format
This is a problem with one of the dependencies, and affects Maverick
too, but not Lucid:
https://b
On 21 July 2010 10:14, martin f krafft wrote:
> PNG works, DjVu/PS or Session does not!
Can you save a PDF with PNG compression?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Can you save any type of file from gscan2pdf? PNG? DjVu?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
tags 504885 pending
thanks
Thanks for the patch
signature.asc
Description: Digital signature
On Tue, Dec 01, 2009 at 08:23:52AM -0800, Michael Vrable wrote:
> For me, the problem went away when ImageMagick was upgraded from
> version 7:6.5.5.3-1 to 7:6.5.7.8-1. (But I haven't tried
> downgrading to verify that the problem returns with the old
> version.)
That is excellent news. Is anyone
severity 538233 normal
tags 538233 moreinfo
thanks
Can you compare the versions of gscan2pdf and its dependencies on your
sid (non-working) desktop and ubuntu (working) laptop?
signature.asc
Description: Digital signature
On Tue, Nov 17, 2009 at 04:30:18PM +, Stephen Denton wrote:
> Please let me know if I can provide any information that will help to solve
> the problem.
I cannot reproduce this, but it is certainly a problem with
imagemagick, which gscan2pdf uses for image processing. However, in
order to be a
tags 531213 moreinfo
thanks
2009/7/26 Jeffrey Ratcliffe :
> As the PDF creation code hasn't been changed between 0.9.27 and
> 0.9.29, it must be PDF::API2. 0.72 seems to be OK, and 0.73 not.
No. I've tried 0.73 on a couple of machines with no problems.
What is strange is that evidently from the size of th
2009/7/26 Robert Kawecki :
> I've generated PDF files from the same source JPEG image (exact same settings:
> JPEG 95%, downsample to 300DPI) on 2 different versions of gscan2pdf: 0.9.29
> and 0.9.27 (from Ubuntu 9.04 on my laptop).
Thanks for all your investigations.
As the PDF creation code has
2009/7/25 Robert Kawecki :
> gscan2pdf was run as: gscan2pdf --debug >debug.log 2>&1
> What I did was importing a JPEG file (tried many times with arbitrary scanned
> and on-disk images, the problem persists), choosing Save and saving it on disk
> as PDF, 300 dpi, 95 embedded JPEG quality.
> I'm at
Please start gscan2pdf with the --debug option, reproduce the problem, and
post the output from the command line.
On May 30, 2009 11:57pm, Cameron Hutchison wrote:
gscan2pdf hangs when saving files. The progress bar just sits at "Saving
page 1 of 1" and does not advance.
When I downgraded package perlmagick from 7:6.5.1.0-1.1 to
7:6.3.7.9.dfsg2-1+b1 (which also required installing libmagick10), the
save
2009/5/8 Niko Tyni :
> sane-backends 1.0.20 removed SANE_CAP_ALWAYS_SETTABLE, because "is _not_ part
> of the current
> stable API."
The really frustrating part about this is that when I wrote the
bindings, I deliberately started with SANE 1.0.19, and not what was in
HEAD. I expected, therefore,
) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * debian/rules:
++ Don't fail when perl is smart enough not to create empty dirs. (Closes:
+ #479922)
+
+ -- Jeffrey Ratcliffe <[EMAIL PROTECTED]> Fri, 30 May 2008 22:40:15 +0200
+
libxml-sax-writer-perl (0.50-1.1) unstable;
.orig/debian/changelog
+++ renrot-0.25/debian/changelog
@@ -1,3 +1,10 @@
+renrot (0.25-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix FTBFS against Perl 5.10 (closes: #479934)
+
+ -- Jeffrey Ratcliffe <[EMAIL PROTECTED]> Thu, 29 May 2008 22:05:34 +0200
+
renrot (0.25-1) un
Non-maintainer upload.
+ * Fix bug compressing empty files (closes: #464205)
+
+ -- Jeffrey Ratcliffe <[EMAIL PROTECTED]> Wed, 21 May 2008 20:55:33 +0200
+
libcompress-bzip2-perl (2.09-1.1) unstable; urgency=low
* Non-maintainer upload.
> the packages for tesseract 2.0 have changed, and tesseract-ocr now
> provides some of the same files that tesseract-ocr-data 1.02-3 provided.
> This makes the 2.0 package un-installable for those that have
> tesseract-ocr-data 1.02-3 installed due to a file conflict.
tesseract-ocr 2.01 depends
58 matches
Mail list logo
