Bug#826131: closed by Norbert Preining <prein...@logic.at> (Re: Bug#826131: texlive-base: tlmgr "cannot setup TLPDB" and doesn't open/update because of that)

[c.buhtz]

Hi Norbert

On 2016-06-02 15:21 ow...@bugs.debian.org (Debian Bug Tracking System)
wrote:
> #826131: texlive-base: tlmgr "cannot setup TLPDB" and doesn't
> open/update because of that

Of course I know the USER MODE and have read the part of the
documentation! That wasn't the case of the bugreport - but I think it
was quite unspecific. Sorry for that.

Please correct me if I am wrong:
The user mode is to handle secondary TexLive installations beside the
main one. So you can have multiple TeXLive installations on one system.
Correct?
But the user mode is not able to touch the main installation. Correct?

Having more than one TeXLive at the same machine sounds quite exotic
for me. :) Anyway.
Of course I just want to manage (update) the main installation -
nothing more.

Do you say that there is no way to manage the main installation with
tlmgr on a Debian system?
If it is so than the error message should be much more precise. kind
of: "Running on Debian. Switching to user mode. Keep in mind that tlmgr
can not manage the main installation. Use the Debian package system
(apt) to update your main TeXLive installation."

What do you think?

Or just kill the tlmgr (like Ubuntu does) to prevent such
missunderstandings.

Bug#824857: no password question after wakin up from hibernate

[c.buhtz]

Package: lxqt-session
Version: current Debian testing
Severity: important
Tags: security

I am using an up-to-date Siduction (paintitblack) with LXQt.

The screensaver is setup to ask a password before resume. This works
well.

But when I wake up from hibernate there is no password question.
This is quite unsecure.

Bug#836300: more conrete wish

[c.buhtz]

Let me more concrete here:

The current version of the package should be deleted.

But it would be a much more better solution if someone would bring the
package up to the current upstream version. Some bugs could be closed
then - I hope.

Bug#814499: status?

[c.buhtz]

What is the current status?

The current version doesn't fit to upstream.

Bug#850805: not enough frames to estimate rate

[c.buhtz]

Maybe this BugReport on Upstream is related to that?

Bug#850805: not enough frames to estimate rate

[c.buhtz]

Package: unpaper
Version: 6.1-2

I am using Debian unstable, scanning papers with gscan2pdf which using
unpaper to detect borders of the paper.

But this doesn't work because of that message

$ gscan2pdf
ERROR - [ppm_pipe @ 0x8a8780] Stream #0: not enough frames to estimate
rate; consider increasing probesize [image2 @ 0x8ab5a0] Using
AVStream.codec to pass codec parameters to muxers is deprecated, use
AVStream.codecpar instead. [image2 @ 0x8ab5a0] Encoder did not produce
proper pts, making some up.

ERROR - Error running unpaper: [ppm_pipe @ 0x8a8780] Stream #0: not
enough frames to estimate rate; consider increasing probesize [image2 @
0x8ab5a0] Using AVStream.codec to pass codec parameters to muxers is
deprecated, use AVStream.codecpar instead. [image2 @ 0x8ab5a0] Encoder
did not produce proper pts, making some up.

Bug#850804: report bug crashes

[c.buhtz]

Package: reportbug
Version: 7.1.2

I am using Debian unstable and tried to send a bugreport for "unpaper".

When when I enter a "brief description" (I think this is the subject of
the bug report) and then click on the "next" button. The window closes.
No error message in the gui.
But the console says:

$ reportbug
Traceback (most recent call last):
  File "/usr/bin/reportbug", line 2233, in 
main()
  File "/usr/bin/reportbug", line 1107, in main
return iface.user_interface()
  File "/usr/bin/reportbug", line 2149, in user_interface
package, severity, mode, charset=charset, tags=tags)
  File "/usr/bin/reportbug", line 182, in handle_editing
editor, charset)
  File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line
1561, in func op = klass(parent)
  File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line
539, in __init__ self.widget = self.create_widget()
  File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line
1173, in create_widget expander = Gtk.Expander("Other system
information") TypeError: GObject.__init__() takes exactly 0 arguments
(1 given)

Bug#869277: /usr/bin/notify-send: Improve the manpage

[c.buhtz]

Related to

 - "libnotify-bin: add informations about upstream"
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869409

 - "libnotify-bin: option -a is not described in notify-send man page"
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756151

 - "Missing man page for notify-send"
   https://bugzilla.gnome.org/show_bug.cgi?id=757151

 - "add valuable informations to README"
   https://bugzilla.gnome.org/show_bug.cgi?id=785286

Just to be clear: IMO a Debian maintainer shouldn't waste it's time
with pimp up the bad documentation of some projects. It is up to
upstream!

Bug#869409: libnotify-bin: add informations about upstream

[c.buhtz]

Hello Andreas

> The information you're interested in seems to fit into
> the "debian/upstream/metadata" descriptions which you can find out
> more about at https://wiki.debian.org/debian/upstream
> Patches welcome!

This is up to upstream to provide that informations.
https://bugzilla.gnome.org/show_bug.cgi?id=785316

I can not understand why this package was accepted for Debian without
providing this minimal informations.

Bug#869277: /usr/bin/notify-send: Improve the manpage

[c.buhtz]

On 2017-07-22 07:19 Jason Crain  wrote:
> On Sat, Jul 22, 2017 at 01:52:49PM +0200, Christian Buhtz wrote:
> > I tried to contribute but can not find the sources of the manpage
> > (for notify- send) somewhere.  
> 
> The manpage is Debian-specific so it's in Debian's pkg-gnome SVN:
> https://anonscm.debian.org/viewvc/pkg-gnome/desktop/unstable/libnotify/debian/

Thanks for the hint. So upstream doesn't offer a manpage?

Sorry but IMO it is wasting ressource when contributing to
distro-specific sources. When upstream would over a manpage I would
contribute to it.

Can you describe the packaging process please? Isn't there a check
if the binary features fit to the manpage and other docs? I would
totally understand if this would be to much work.

I know I am quite radical here: I would suggest to kill the debian
specific manpage, put enough pressure on upstream to offer its own
manpage. If not kill the complete package because of Debian-quality.

Bug#869277: Acknowledgement (/usr/bin/notify-send: Improve the manpage)

[c.buhtz]

On 2017-07-22 10:27 ow...@bugs.debian.org (Debian Bug Tracking System)
wrote:
> Thank you for filing a new Bug report with Debian.
> 
> You can follow progress on this Bug here: 869277:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869277.
> 
> This is an automatically generated reply to let you know your message
> has been received.
> 
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
> 
> Your message has been sent to the package maintainer(s):
>  Debian GNOME Maintainers
> 
> 
> If you wish to submit further information on this problem, please
> send it to 869...@bugs.debian.org.
> 
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
> 

Bug#871266: debug output

[c.buhtz]

The last lines of the debug output


procheader.c:155:generic_get_one_field: empty line
tnef_parse.c:295:Tnef parser parsing part (41902).
tnef_parse.c:297:content: /home/user/.claws-mail/mimetmp/claws.4I0P4Y
Attempting to parse /home/user/.claws-mail/mimetmp/claws.4I0P4Y...
suspecting a corrupt file in UTF8 conversion


They indicate a problem with the TNEF-PlugIn. When deactivating it
claws-mail works without problems.

So this is related to the package "claws-mail-tnef-parser".
I will wait for maintainers advise.

Bug#744801: close

[c.buhtz]

Can you still reproduce this behaviour with the current 1.12 version in
Debian or with the 1.20 version from git?

I vote for closing this bug.

Bug#607758: github issue

[c.buhtz]

Because upstream moved from launchpad to GitHub the upstream-bug is no
here https://github.com/bit-team/backintime/issues/199

Bug#863499: [Pkg-xfce-devel] Bug#863499: Trash: sort the files/folders by "time of deletion"

[c.buhtz]

On 2017-05-28 21:42 Yves-Alexis Perez  wrote:
> What about sorting by modification date?

Not really working.
 - The folders are shown on top. That can only be deactivated for all
   folders and not for Trash only.
 - From the users point of view is the "modification date" not the
   deletiton date. If it is technical the same: Just rename that
   menupoint it when Trash is shown.

regards

Bug#816197: close

[c.buhtz]

Please close this bug because it is fixed.

Bug#866741: offer debug output

[c.buhtz]

Can you offer the debug output please?

Start backintime from comanndline.

backintime-qt --debug

Bug#874024: the attachment

[c.buhtz]

Here is the file causing the problem in the parser

claws.KURU5Y
Description: Binary data

Bug#882510: reopen

[c.buhtz]

Please explain why you closed?

The error message is still there. No fix.

You just gave a workaround with choosing a View.

Bug#893251: jabref 3.8 is started with OpenJDK 9 instead of 8

[c.buhtz]

Dear Gregor,

thank you very much for your fast reply.

> True, this is already reported as #890905/#893138.
> I ('m trying to) merge those two bugs.

Sorry, for reporting again. I noticed that bugs. But as a
Java-foreigner it wasn't clear for me if they address the same issue.

> You can run
> JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ jabref

Something is wrong here. Did openjdk-8 changed a bit?

$ JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ jabref
Exception in thread "main" java.lang.NoSuchMethodError:
java.nio.ByteBuffer.flip()Ljava/nio/ByteBuffer; at
org.apache.logging.log4j.core.appender.OutputStreamManager.flushBuffer(OutputStreamManager.java:292)
at
org.apache.logging.log4j.core.appender.OutputStreamManager.flush(OutputStreamManager.java:303)
at
org.apache.logging.log4j.core.appender.OutputStreamManager.closeOutputStream(OutputStreamManager.java:308)
at
org.apache.logging.log4j.core.appender.OutputStreamManager.releaseSub(OutputStreamManager.java:137)
at
org.apache.logging.log4j.core.appender.AbstractManager.stop(AbstractManager.java:86)
at
org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.stop(AbstractOutputStreamAppender.java:142)
at
org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.stop(AbstractOutputStreamAppender.java:136)
at
org.apache.logging.log4j.core.config.AbstractConfiguration.stop(AbstractConfiguration.java:359)
at
org.apache.logging.log4j.core.AbstractLifeCycle.stop(AbstractLifeCycle.java:136)
at
org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:550)
at
org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:617)
at
org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:634)
at
org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:229)
at
org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:153)
at
org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
at
org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:122)
at
org.apache.logging.log4j.jcl.LogAdapter.getContext(LogAdapter.java:39)
at
org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:46)
at
org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:40)
at
org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:55)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:655) at
net.sf.jabref.JabRefMain.(JabRefMain.java:37)



signature.asc
Description: Digital Signature

Bug#926074: RSS-Feed: Server ignores 'Last-Modified' date

[c.buhtz]

Dear Raphael,

thanks for that quick reply.

On 2019-04-01 22:00 Raphael Hertzog  wrote:
> We are relying on a Django object to implement the feed so if
> anything, this should be improved at this level:
> https://docs.djangoproject.com/en/1.11/ref/contrib/syndication/
> 
> I would suggest to file your suggestion to the Django developers.

I have no idea about Django - never used it and even not sure what it
is. Because you are the Django users I would suggest you should fill a
bug report or anything like that.

On 2019-04-01 22:00 Raphael Hertzog  wrote:
> Unless Django expects us to setup a ConditionGETMiddleware to replace
> the answer by a NotModified answer:

No idea what you talking about. ;) Don't know what a "middleware" is.

Bug#926341: close

[c.buhtz]

Please close. Sorry.

https://github.com/keepassxreboot/keepassxc-browser/issues/375#issuecomment-479590355

Bug#926073: [reportbug-ng] "version information" should be filled automatic

[c.buhtz]

Package: reportbug-ng
Severity: minor

--- Please enter the report below this line. ---

When creating a new bug report a dialog opens. The first field is the
package-name. The second one is the "version".

It should be easy to check the currently installed version of the
package and pre-fill that information in that field.

--- System information. ---
Architecture: 
Kernel:   Linux 4.9.0-8-amd64

Debian Release: 9.8
  500 stable-updates  ftp.tu-chemnitz.de 
  500 stable  security.debian.org 
  500 stable  ftp.tu-chemnitz.de 
  500 stable  deb.debian.org 
  100 stretch-backports ftp.debian.org 

--- Package information. ---
Depends   (Version) | Installed
===-+-==
python:any(>= 2.7.5-5~) | 
python-debianbts   (>= 1.0) | 2.6.1
python-pyqt5| 5.7+dfsg-5
python-pyqt5.qtwebkit   | 5.7+dfsg-5
xdg-utils   | 1.1.1-1+deb9u1
xterm   | 327-2
python-apt  (>= 0.7.93) | 1.4.0~beta3


Package's Recommends field is empty.

Package's Suggests field is empty.

Bug#926072: [reportbug-ng] Unclear what "WNPP" means

[c.buhtz]

Package: reportbug-ng
Severity: minor

--- Please enter the report below this line. ---

The GUI doesn't tell the user what "WNPP" means. Please add this
information e.g. as tooltip.

--- System information. ---
Architecture: 
Kernel:   Linux 4.9.0-8-amd64

Debian Release: 9.8
  500 stable-updates  ftp.tu-chemnitz.de 
  500 stable  security.debian.org 
  500 stable  ftp.tu-chemnitz.de 
  500 stable  deb.debian.org 
  100 stretch-backports ftp.debian.org 

--- Package information. ---
Depends   (Version) | Installed
===-+-==
python:any(>= 2.7.5-5~) | 
python-debianbts   (>= 1.0) | 2.6.1
python-pyqt5| 5.7+dfsg-5
python-pyqt5.qtwebkit   | 5.7+dfsg-5
xdg-utils   | 1.1.1-1+deb9u1
xterm   | 327-2
python-apt  (>= 0.7.93) | 1.4.0~beta3


Package's Recommends field is empty.

Package's Suggests field is empty.

Bug#893253: Is it still reproducible?

[c.buhtz]

On 2019-11-09 11:19 Changwoo Ryu  wrote:
> Is it still reproducible with recent versions of ibus and clients?

My main problem with JabRef is gone. I can insert 日本語 without a
problem.

But "Anki" (current upstream and official-deb-repository version) still
does not work. Do not understand why. Maybe this is a app specific
problem.

Bug#946788: (no subject)

[c.buhtz]

Upstream bug report can be found here

https://github.com/kurtmckee/feedparser/issues/198

Bug#960771: firefox-esr: Settings modified after package updates

[c.buhtz]

The problem is still in the current Firefox 78.6.0esr (64-Bit)

One "affected setting" is not a problem anymore:
 - The hiding of the toolbar buttons. I show them all by default. After
   an update they are hidden again behind a right-double-arrow button.

But this two things still happens.

 - Keywords for the search engines. They are set back to
   install-default after an package update.
 - Deleted search engines (e.g. amazon, ebay, google, bing) are back
   again after an package update.

Bug#860890: (no subject)

[c.buhtz]

The described problems still exists.

The problem is transparency. No matter if this is an issue for an admin
and this has to be very complex and nerdy or something like this
because of that.

The problems and issues need to be reported and documented, even for
Debian.

A much more user- and admin-friendly and polite reaction would be to
do the adduser command by default when installing the package.

Is there any good reason why this could not happen by default?

Bug#1022231: iptables-persistent: Pre-existing /etc/iptables/rules.v4 is overriten when installing

[c.buhtz]

But silently overriding isn't a solution.

> if you ask the package to save the rules it will save them, it is the
> expected behaviour

But overriding isn't expected.

Then warn the user about that overriding.

And one other bug is that it tries to "save rules" and ask about that
even if there are not active rules.

> iptables rules are order dependent

I know but the user need to care about it not a package maintainer.

Bug#1019446: kde-config-cron: Binary missing

[c.buhtz]

Dear Bernhard,

thanks for the reply.

On 2022-09-24 10:09 Bernhard Übelacker  wrote:
> I guess the kcm_cron.so is really just like a module
> loaded by systemsettings5.

"systemsettings" and "systemsettings5" does not exist on my system and
not in the repos (via "apt-cache search").

It seems to me that the package "kde-config-cron" has some missing
dependencies.

Bug#1027823: (no subject)

[c.buhtz]

Damn, I was wrong about the Freeze date. It isn't the 23th but the 13th
- in 5 days.

Bug#998105: Fix published (see pull request)

[c.buhtz]

On 2023-03-05 19:52 Sven Geuer  wrote:
> On Fri, 2023-03-03 at 01:46 +0100, BiT dev wrote:
> > [...]
> > https://github.com/bit-team/backintime/pull/1413
> > [...]
> 
> I created a patch to backintime 1.3.3-4 and tested it successfully.
> 
> Here is the merge request for a backintime 1.3.3-5:
> https://salsa.debian.org/jmw/pkg-backintime/-/merge_requests/9

Dear Sven,

this is one of the upstream maintainers (@buhtz).

Thanks a lot for your contribution. Keep in mind the the upstream PR
isn't merged yet.

And wouldn't it be better to use the next upstream release instead of a
Debian specific patch?

We have no problem to prepare a upstream 1.3.4 if Jonathon (or Fabio)
tell us that this is used for Debian 12 and not blocked because of the
current freeze.

We'll wait for advice.

Kind
Christian Buhtz

Bug#940319: (no subject)

[c.buhtz]

Dear Jonathan,

with help from the DPT I realized what is going on here.

I had the wrong assumption that all Debian packages do run some kind of
tests. I couldn't imagine it that Debian, which stands for high
quality, do accept untested packages in its repo.

That is why this ticket was kind of urgent to me. I didn't realized
that BIT never had running tests at Debian. I thought the tests are
"just broken".

Please don't wast your time on workaround this ticket. It is just the
tip of the iceberg. Our upstream tests do work with SSH server,
generating SSH key pairs, installing them, running rsync, running other
backintime processes, etc. Find a solution for writing to HOME won't
save all problems.

We do discuss this at upstream
https://github.com/bit-team/backintime/issues/1489

My plan is to separate our test suite into unit, integration and system
tests. Then you will be able to run just the unit tests.

I do suggest making this ticket a "minor bug" instead of "wishlist". It
is IMHO a bug having an untested package in Debian. "Minor" is a
compromise. I would make it "grave". :)

Kind
Christian

Bug#1043046: (no subject)

[c.buhtz]

Dear Armin,
thanks for reporting back.

There really might be a problem with converting the config file between
BIT 1.2.1 and 1.3.3. I have to investigate this further and try to
reproduce it.

It might be a serious problem to everyone upgrading from Debian 11 to
12 and using "Repeatedly (anacron)" as schedule option.

Do you still have access to your old config file from BIT version
1.2.1? This would be really helpful.
If not can you tell me exactly how do you setup your profile with BIT
1.2.1? It was setup to "Repeatedly (anacron)"? Each N
hours/days/weeks/months?
Was it a local/local (encrypted)/SSH/SSH (encrypted) profile?

Thanks in advance
Christian

Bug#1066899: wiki.debian.org: Missing definition (link) about "git-dpm project"

[c.buhtz]

Thanks for reaching out.

On 2024-03-19 10:41 Boyuan Yang  wrote:
> I don't think there is such a definition.

That is the problem.

> According to my
> understanding, the "git-dpm project" solely means ...
> [..]
> Please feel free to rephrase it, edit the Wiki page as
> needed

No I don't "feel free" because I am not the expert.

Please do it on your site or find an expert how has the expertise to
explain that term.

In the current state that wiki page harm the project more then it helps.

Kind
Christian

Bug#924889: (no subject)

[c.buhtz]

The same problem goes for this page.

Bug#1067949: www.debian.org: No language selection on "www.debian.org/doc/manuals/maint-guide/"

[c.buhtz]

Dear Holger,

Thanks for work on that ticket.

But this does not solve the problem that this language links are
missing.

Having this links directly in the footer of such pages would increase
the usability.

Kind,
Christian