Bug#987176: Same on Debian 11.1
Same here with Debian 11.1 just installed with netinst ISO. Very bad for out-of-the-box user experience. Mauro Molinari
Bug#884262: flashplugin-nonfree: link to Adobe Flash Player not found on http://www.adobe.com/
Same problem on Jessie. Mauro
Bug#840634: flashplugin-nonfree: Failed to download fp.11.2.202.637.sha512.amd64.pgp.asc
Same problem here, I can't update the Flash Player plugin, but with an additional oddity. This morning, running: update-flashplugin-nonfree --status was producing the following output: Flash Player version installed on this system : 11.2.202.635 Flash Player version available on upstream site: 23.0.0.205 flash-mozilla.so - auto mode link currently points to /usr/lib/flashplugin-nonfree/libflashplayer.so /usr/lib/flashplugin-nonfree/libflashplayer.so - priority 50 Current 'best' version is '/usr/lib/flashplugin-nonfree/libflashplayer.so'. Version 23.0.0.205?? :-O After running "aptitude reinstall flashplugin-nonfree", now the result is: Flash Player version installed on this system : 11.2.202.635 Flash Player version available on upstream site: 11.2.202.643 flash-mozilla.so - auto mode link currently points to /usr/lib/flashplugin-nonfree/libflashplayer.so /usr/lib/flashplugin-nonfree/libflashplayer.so - priority 50 Current 'best' version is '/usr/lib/flashplugin-nonfree/libflashplayer.so'. If now I run "update-flashplugin-nonfree -vi", I see that it downloads successfully a file at https://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/fp10.sha512.amd64.pgp.asc, which however refers to version 11.2.202.635 of the Flash Player, rather than to version 11.2.202.643. The net result is that the Flash Player is not updated. Mauro
Bug#810735: fatresize: fails to open /dev/mmcblk0p1
I also encountered this problem on Linux Mint 17.3, based on Ubuntu Trusty, fatresize version is 1.0.2-6ubuntu1.
Bug#728375: libjetty8-java-doc: Questionable dependencies
Il 09/10/2014 09:47, Jan Henke ha scritto: Hi, I do think it is reasonable to assume that installing an optional documentation package of one component normally also installs the documentation for other related packages. Especially it does seem to be logical to have default-jdk-doc installed when you install the documentation of jetty. As such I am in favour of keeping the current recommends. For sure the default behaviour does not suit every use case, but I do not think changing the default should be done. I still think the current default is the expected behaviour. Just to say that my opinion was based on the fact that I am an experienced Java developer. I really don't need the JDK docs just to read the Jetty 8 Javadoc. I would assume that if one needs to use the Jetty API in its own application already knows what a "String" or an "IOException" is, just to mention the first two JDK classes that come into my mind. So, it's just a "logical" vs "practical" approach. Maybe "suggests" would keep the logical relationship between packages without unexpected practical consequences on the weight of the size on disk (almost 8x) and download (almost 12x). After all, the Jetty 8 Javadoc is self-contained, as it is viewable online at: http://download.eclipse.org/jetty/stable-8/apidocs/ Even if references towards JDK classes didn't work, they won't limit the usability of the documentation in a substantial way. By the way, I was wondering if inter-javadoc package references work if I install all of those 300 MB of packages (do the downloaded HTML files contain file:// absolute paths to get to the proper Javadoc files in the Debian filesystem structure? I can't test now). Mauro -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#728375: libjetty8-java-doc: Questionable dependencies
Il 06/10/2014 12:09, Emmanuel Bourg ha scritto: libjetty8-java-doc already recommends default-jdk-doc, maybe you meant "suggested" instead? I may have used the wrong terms here, sorry. What I find questionable is that, as I said in my original report, if I try to install libjetty8-java-doc, APT by default says it will install other Javadoc packages as well, for a total of almost 300MB of data... I don't think these dependency Javadoc packages are actually needed for me to read the Jetty 8 documentation. They might be "useful" in some cases, but nothing more. I just learnt I can use --no-install-recommends apt-get parameter (I expect aptitude to have something similar) to filter out recommended packages, but that's not what I would expect by default. This is just my opinion. Thanks for your feedback! Mauro -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#728375: libjetty8-java-doc: Questionable dependencies
Il 31/10/2013 14:07, Emmanuel Bourg ha scritto: The JDK documentation alone uses about 240 MB. Almost all Java documentation packages depend on this, but you have to pay the price only once. The dependency is necessary to have nice links between the Javadoc of the package specific classes and the Javadoc of the core Java classes. I see, but couldn't these dependencies just be "recommended"? I know it's a stupid reason, but if you install jetty8 and libjetty8-java-doc and you configure Jetty to start, a welcome page for Jetty in Debian is deployed in the server instance with a link to the Jetty 8 Javadoc. Even if we assume that this link works (I just reported another bug for that), it means that to just have that "example webapp" working correctly you'll have to download 240 MB of documentation which I doubt would even work from within the Jetty instance itself, because links to JDK or Servlet Javadocs would point to files outside the Jetty 8 configured directories (I didn't try, though). Also, if you just install the jetty8 package without the libjetty8-java-doc one, you'll get a default welcome page in Jetty with a link to some missing contents (=> the Javadoc documentation, as said). This however doesn't justify a strong dependency between jetty8 and libjetty8-java-doc just for a simple hyper-linking issue. Anyway, I'm not so presumptuous to suggest to change a convention used for all the Debian packages for javadoc documentation sets, I just wanted to give my 2 cents on this. Mauro -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#728380: jetty8: Missing files
Package: jetty8
Version: 8.1.3-4
Severity: important
Dear Maintainer,
I think some files are missing from jetty8 package.
First of all, the official Jetty documentation talks about a context deployer
which monitors the ${jetty.home}/contexts directory to hot deploy webapps
configured using appropriate xml files. The jetty8 Debian package provides such
a directory in etc/jetty8/contexts, also providing an example javadoc.xml file
which should allow to deploy the Jetty javadoc provided by libjetty8-java-doc
package. However, there's no jetty-*.xml file in /etc/jetty8 which configures
the ContextDeployer (or rather the ContextProvider, see below).
The provided file /etc/jetty8/contexts/README.TXT says that the ContextDeployer
is configured in jetty.xml configuration file, but if you look at the contents
of this file you'll see this is not the case. Also, if you start jetty8 with
all the default contents, a welcome page is displayed which points to the
javadoc, but this link does not work at all (even if you install
libjetty8-java-doc) because the ContextDeployer is not actually configured.
/etc/jetty8/jetty-plus.xml also says ContextDeployer is configured in jetty.xml.
/ety/jetty8/jetty-shared-webapps.xml configures just the WebAppDeployer,
although a comment says: "see ContextDeployer above"... but it's not there,
either.
Also, reading the offical Jetty 8 documentation at
http://download.eclipse.org/jetty/stable-8/apidocs, you'll see that
WebAppProvider and ContextProvider should be used rather than WebAppDeployer
and ContextDeployer, which are old and deprecated. So I would expect the Debian
package to use the new classes, just like the official Jetty distribution ZIP
file does (I checked that this was the case even in the old 8.1.3 distribution
package, so it's not an issue with the old Jetty version packaged in Debian).
Another little error I saw is again in /etc/jetty8/jetty-shared-webapps.xml:
the starting comment says that it configures Jetty to deploy webapps in
/usr/share/java/webapps, but it should actually say /usr/share/jetty8/webapps.
Lastly, the libsetuid.so for Jetty 8 is missing, because there isn't any
package corresponding to libjetty-extra used for Jetty 6.
-- System Information:
Debian Release: 7.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages jetty8 depends on:
ii adduser 3.113+nmu3
ii apache2-utils2.2.22-13
ii default-jre-headless [java6-runtime-headless]1:1.6-47
ii libjetty8-java 8.1.3-4
ii openjdk-6-jre-headless [java6-runtime-headless] 6b27-1.12.6-1~deb7u1
jetty8 recommends no packages.
Versions of packages jetty8 suggests:
pn libjetty8-extra-java
pn libjetty8-java-doc
-- Configuration Files:
/etc/default/jetty8 changed:
VERBOSE=yes
JETTY_HOST=0.0.0.0
JETTY_PORT=8080
JETTY_SHUTDOWN=300
JAVA_OPTIONS="-Xmx256m -Djava.awt.headless=true"
JDK_DIRS="/usr/lib/jvm/default-java"
JSP_COMPILER=javac
JETTY_TMP=/var/cache/jetty8
LOGFILE_DAYS=30
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#728375: libjetty8-java-doc: Questionable dependencies
Package: libjetty8-java-doc
Version: 8.1.3-4
Severity: important
Dear Maintainer,
if I try to do the following on my system:
aptitude install libjetty8-java-doc
the system says (I'm translating from Italian):
The following NEW packages will be installed:
default-jdk-doc{a} libgnuinet-java{a} libgnujaf-java-doc{a}
libgnumail-java-doc{a} libjetty8-java-doc libservlet2.5-java-doc{a}
openjdk-6-doc{a}
0 updated packages, 7 installed, 0 to remove and 0 outdated.
It's necessary to download 23.6 MB of archives. After extraction, they will use
274 MB.
Continue? [Y/n/?]
Well, 274 MB to install a package which just contains some HTML pages (the
Javadoc for Jetty 8) seems quite too much to me...
After all, I don't think I need any of those packages to simply browse that
documentation.
I'm still a novice for Debian, so please don't blame on me if my report is not
appropriate.
-- System Information:
Debian Release: 7.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
