.
Before issuing that error message, CUPS should check against a list of
common schemes and give a message about enabling the scheme if the
scheme is on the list. The list should included any that appear in the
CUPS documentation.
- --
Liam Morland l...@morland.caCanadian Scout Camps
/show_bug.cgi?id=692822
- --
Liam Morland l...@morland.caCanadian Scout Camps Directory
http://Liam.Morland.ca/ http://ScoutDocs.ca/Camps/
PGP Public Key: http://liam.morland.ca/pgp-public-key.asc
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux
://user:passw...@example.com/feed
lkmorlan@burns:~$ r2e run
processing error: 'str' does not support the buffer interface: example
(http://user:passw...@example.com/feed - lkmorlan)
lkmorlan@burns:~$
--
Liam Morland l...@morland.caCanadian Scout Camps Directory
http://Liam.Morland.ca
lkmorlan@burns:~$ r2e new lkmorlan
lkmorlan@burns:~$ r2e add example http://user:passw...@example.com/feed
lkmorlan@burns:~$ r2e -VVV run
load feed configuration from ['/etc/xdg/rss2email.cfg',
'/home/lkmorlan/.config/rss2email.cfg']
loaded configuration from
2014-09-01 15:02-0700 W. Trevor King wk...@tremily.us wrote:
Ah, that's because 'example.com/feed' isn't giving you an RSS or Atom
feed ;). The ‘processing error’ reports are rss2email passing along a
bozo exception [1]. If you can reproduce that error for a real feed
(i.e. not
2014-09-01 16:16-0700 W. Trevor King wk...@tremily.us wrote:
No headers? No recognized version? Are you sure this is a valid feed?
Can you show us the headers you *are* getting? For example:
lkmorlan@burns:~$ wget --user=lkmorlan --password='passwd' -S
and rss2email for Debian, so you may not actually
need to file a new bug ;).
Thanks very much, Trevor.
Etienne, it is convienent that you maintain both packages. I'll leave it
to you.
Liam
--
Liam Morland l...@morland.caCanadian Scout Camps Directory
http://Liam.Morland.ca
Why is there a limitation at all? Bytes are just bytes; why does there have to
be a newline character every so often? I have lost mail because of this rule.
Please fix.
Silently bouncing messages mean messages can get lost. For example, when I
fetch manually, I can see this:
fetchmail: SMTP error: 550 maximum allowed line length is 998 octets, got 1006
fetchmail: mail from MAILER-DAEMON@ bounced to
fetchmail: SMTP listener refused delivery
If fetchmail is
For the reference of others having this problem:
I was able to upgrade by using pg_upgrade instead of pg_upgradecluster,
following the instructions here:
https://wiki.postgresql.org/wiki/Using_pg_upgrade_on_Ubuntu/Debian
The upgrade maintained the NOT VALID constraints.
I could also have used
I just solved a problem very similar to this. It was caused by the
spring 2019 Debian upgrade. To solve it, I added "oldstable" to my
Debian sources.list and then I was able to downgrade several packages. I
downgraded:
printer-driver-hpcups to 3.16.11+repack0-3
ghostscript, ghostsctipt-x,
During each failed save attempt, an empty file appears in the directory
that I am trying to save in. The files have names like:
lu9017o81.tmp
lu91531wjf.tmp
lu93939glt.tmp
2020-07-23 01:08-0400 Rene Engelhard wrote: [...]
>Opened LibreOffice Writer, typed "Test" in the document and saved it
>into Test.odt. [...]
That is the exact test I did.
>Any special thing? Big or small? [...]
It happens this way for any document I have tried. I haven't tried any
large
I have observed this bug as fixed in Debian testing.
I had the same problem trying to upgrade from postgresql 11 to 13. I got
the same "ee key too small" error.
pg_upgradecluster exited without creating a working upgrade and without
giving an error message. It did not appear to fail.
I dropped the non-working pg 13 cluster and then ran:
sudo
at any email address in abook is whitelisted in my
spam filter. If there is no local part, the entire domain is
whitelisted.
On the principle that software should be "strict when sending and
tolerant when receiving", it is not being strict to output an invalid
email address.
Regards,
16 matches
Mail list logo
