On 14/09/13 01:19 PM, Fòram na Gàidhlig wrote:
tuxpaint:
http://tuxpaint.cvs.sourceforge.net/viewvc/tuxpaint/tuxpaint/src/po/
Thanks. My preference is to have upstream release with the updated
translations. I will pursue that first, but if that cannot happen in a
timely fashion, will review
On 14/09/13 02:44 PM, Fòram na Gàidhlig wrote:
So would I, but we haven't had any luck so far. Maybe they will listen
to you and find the time - there is always hope!
Ironically when you make software for kids and then *have* kids, finding
that time becomes a big challenge. So upstream
On 07/09/13 06:30 PM, Alejandro Garrido Mota wrote:
taskd is in alpha version and should not be in unstable, initially. I
think that experimental is good branch for taskd. What do you think?
Sure, that sounds good.
Your welcome... and now vramsteg is in unstable :)
Yes! And in fact, it was
Alejandro,
I was discussing your ITP of taskd with upstream because we noticed you
had filed this and a handful of other ITPs of tasktools.org software.
What is your plan for this? Upstream believes it is not really suitable
to package yet as it is only barely in beta.
Thanks for your work on
Package: wnpp
Severity: wishlist
Owner: Ben Armstrong sy...@sanctuary.nslug.ns.ca
* Package name: libjs-tinycon
Version : 0.5
Upstream Author : Tom Moor tom.m...@gmail.com
* URL : https://github.com/tommoor/tinycon
* License : MIT
Programming Lang: Javascript
Jérémy,
Thanks for reviewing this.
On 26/08/13 03:38 PM, Jérémy Bobbio wrote:
Packaged in libjs-twitter-bootstrap.
Check out my work in progress in git. You'll find I already depend on this.
Ben Armstrong:
lib/taskwarrior-web/public/css/datepicker.css
lib/taskwarrior-web/public/js
Package: opennebula
Followup-For: Bug #720038
I guess there's some level of awareness that opennebula needs this, as I
just found:
http://bugs.debian.org/719601
Ben
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Package: gem2deb
Version: 0.4.1
Followup-For: Bug #712851
This is probably an adequate test:
find . -maxdepth 1 -iname version
i.e. if it finds (case-insensitively) a 'version' file in the top dir,
warn (summarizing / linking to a proposed solution)
--
To UNSUBSCRIBE, email to
Package: wnpp
Severity: wishlist
Owner: Ben Armstrong sy...@sanctuary.nslug.ns.ca
* Package name: ruby-parseconfig
Version : 1.0.2
Upstream Author : BJ Dierkes de...@bjdierkes.com
* URL : https://github.com/derks/ruby-parseconfig
http://rubygems.org/gems/parseconfig
Package: wnpp
Severity: wishlist
Owner: Ben Armstrong sy...@sanctuary.nslug.ns.ca
* Package name: ruby-rack-flash3
Version : 1.0.3
Upstream Author : Pat Nakajima patnakaj...@gmail.com Travis Reeder
tree...@gmail.com
* URL : https://github.com/treeder/rack-flash
Package: wnpp
Severity: wishlist
Owner: Ben Armstrong sy...@sanctuary.nslug.ns.ca
* Package name: ruby-simple-navigation
Version : 3.11.0
Upstream Author : Andi Schacke andreas.scha...@gmail.com Mark J. Titorenko
* URL : https://github.com/andi/simple-navigation
Package: wnpp
Severity: wishlist
Owner: Ben Armstrong sy...@sanctuary.nslug.ns.ca
* Package name: ruby-sinatra-simple-navigation
Version : 3.6.0
Upstream Author : Andi Schacke andreas.scha...@gmail.com Mark J. Titorenko
* URL : https://github.com/andi/sinatra-simple
Package: wnpp
Severity: wishlist
Owner: Ben Armstrong sy...@sanctuary.nslug.ns.ca
* Package name: ruby-blockenspiel
Version : 0.4.5
Upstream Author : Daniel Azuma daz...@gmail.com
* URL : http://dazuma.github.io/blockenspiel/
http://rubygems.org/gems/blockenspiel
Package: wnpp
Severity: wishlist
Owner: Ben Armstrong sy...@sanctuary.nslug.ns.ca
* Package name: ruby-versionomy
Version : 0.4.4
Upstream Author : Daniel Azuma daz...@gmail.com
* URL : http://dazuma.github.io/versionomy/
http://rubygems.org/gems/versionomy
* License
Package: wnpp
Severity: wishlist
Owner: Ben Armstrong sy...@sanctuary.nslug.ns.ca
* Package name: taskwarrior-web
Version : 1.1.11
Upstream Author : Jake Bell j...@theunraveler.com
* URL : https://github.com/theunraveler/taskwarrior-web
https://rubygems.org/gems
Package: task
Version: 2.2.0-3
Severity: wishlist
Please rename task to reflect upstream's name change from 'task' to
'taskwarrior'. This will make it easier to find for those who know
what they're looking for.
Although the package description contains the new name, which makes it possible
to
On 10/08/13 02:12 PM, Tuxicoman wrote:
I booted on the usb key, the debian installer launch and propose to me to
install or 64 bit install. As I was pretty sure it was a 64 bit machine I
used the last option and then nothing happened except black dots drawn on top
of the screen.
It is not.
Package: cups-browsed
Version: 1.0.34-3
Followup-For: Bug #711229
I understand that in the normal case this is fixed. I guess I'm
abnormal, as I didn't happen to have libnss-mdns, even though I already
have avahi-daemon and normally install recommends.
While finding this bug and manually
On 30/06/13 05:24 AM, Sandro Tosi wrote:
this is described in the How to Use New GTK+ User Interface section
of /usr/share/doc/reportbug/README.Users.gz
...
it seems too much complication to me; I'd rather teach users how to
read programs documentation and how to solve problems instead of
On 21/06/13 10:22 AM, Gonéri Le Bouder wrote:
Package: live-build
Version: 3.0.5-1
Severity: normal
Dear Maintainer,
--debian-installer yes seems to be broken. What I do:
Sorry, but I didn't notice when I asked you to file the bug:
The lb_config man page says 'true' is a valid value and
=Ben Armstrong sy...@sanctuary.nslug.ns.ca
INTERFACE=text
** /u12/home/synrg/.reportbugrc:
reportbug_version 2.20
mode expert
ui text
realname Ben Armstrong
email sy...@sanctuary.nslug.ns.ca
-- System Information:
Debian Release: 7.0
APT prefers stable
APT policy: (500, 'stable')
Architecture
Package: backuppc
Followup-For: Bug #708245
The bug filer hasn't provided the requested info in over two weeks. If TopDir
wasn't defined, how would that happen? Failure to update the config from an
a version created by an even older release? User error? Something else?
My backuppc upgrade from
On 29/05/13 06:07 AM, Johan Lörne wrote:
Package: live-boot
Version: 3.0.1-1
Dunno if i'm doing this correct. I sent my previous bug to the wrong
package apparently, and i'm not sure if this is the right one or if it's
maybe live-config?
I don't have the version number, but it was
Package: live-build
Version: 3.0.5-1
Followup-For: Bug #709887
It's unclear to me where this bug belongs, too. I guess maybe
syslinux-themes-debian, but can't be certain. It appears that live-build
correctly includes /live/memtest, it's just that the syslinux hdt menu
entry expects to find a
Package: debian-live
Severity: normal
Pseudo-bug to track progress. Add blocking bugs for the 7.0.1 release to this.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: live-config
Version: 3.0.23-1
Severity: normal
I found while testing the gnome live RC2 image which contains
live-config 3.0.23-1 that the screensaver still kicks in after a while.
I verified the gnome-screensaver hook was run, but also found that
/var/log/live/config.log contained this:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package live-build
Fixes failure to build netboot image type by removing inclusion
of loadlin for netboot.
unblock live-build/3.0.5-1
-- System Information:
Debian
On 28/04/13 03:08 PM, Adam D. Barratt wrote:
Should we expect a -2 fixing this?
Yes. I expect by tomorrow.
Ben
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
tweak the system while
+d-i is running. See /usr/share/debian-installer-launcher/hooks/README.
+ * Ensure that /run/lock exists in the d-i chroot (mimick what /init does
+in the initrd).
+
+ -- Ben Armstrong sy...@sanctuary.nslug.ns.ca Sun, 28 Apr 2013 17:15:41 -0300
+
debian-installer
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package live-tools
This version supports building a live image on a live system
and fixes an incorrect man page symlink. I have attached a
debdiff with */manpages/*/*
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package live-build
Numerous minor fixes that are nevertheless important for the
release, including wheezy release-specific updates (new wheezy-backports
address scheme,
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package live-config
Includes a fix needed for fglrx/nvidia support in unofficial
non-free images.
unblock live-config/3.0.23-1
-- System Information:
Debian Release: 7.0
On 26/04/13 04:05 PM, Adam D. Barratt wrote:
Is that a particularly common use case?
We support a few users who do most, if not all of their builds this way.
It may not be common, but it's important for the few users who use it.
Ben
--
To UNSUBSCRIBE, email to
On 04/04/13 02:28 PM, ian_br...@fastmail.net wrote:
On Thu, 04 Apr 2013 12:45:55 -0300
Ben Armstrong sy...@debian.org wrote:
Just take care in future that the style of communications you used
triggered someone's wetware spam filter with a false positive.
I initially wrote up a detailed
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package live-config
Fixes one RC bug, #704562, which breaks upgrades from squeeze. Also
includes some translation and spelling fixes and closes a few more
bugs of lesser
+
+ * Use tmpfs and lazy unmount to ensure safe cleanup.
+Thanks to Bastian Blank wa...@debian.org. (Closes: #703979).
+ * Ensure chroot inherits DISPLAY from caller to make
+install from console possible again.
+
+ -- Ben Armstrong sy...@sanctuary.nslug.ns.ca Sat, 30 Mar 2013 10:37:55
Package: debian-installer-launcher
Version: 15
Severity: grave
If umount is prevented for any reason, such as the user opening a shell in
/lib/live/installer/target and then leaving it open, while exiting the
installer, then the cleanup of /lib/live/installer after the install will
remove the
I'm in Uploaders now, so technically I could just upload my (fully
tested) fix. I'd appreciate, however, a review pull before I do.
See:
git clone http://syn.theti.ca/git/debian-installer-launcher.git
gitweb: http://syn.theti.ca/gitweb/?p=debian-installer-launcher.git
Thanks,
Ben
--
To
the
+filesystem using the old criteria. (Closes: #702335).
+ * Adding myself to Uploaders.
+
+ -- Ben Armstrong sy...@sanctuary.nslug.ns.ca Sun, 24 Mar 2013 16:28:46 -0300
+
debian-installer-launcher (14) unstable; urgency=low
[ Updated translations ]
diff --git a/debian/control b/debian
Package: debian-installer-launcher
Version: 14
Followup-For: Bug #702335
I have made some small progress in narrowing down where the failure
occurs. It appears that in plugins/live, fuser is identifying a much
larger list of PIDs than it looks like was intended:
live_cleanup () {
# Stopping
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/25/2013 10:02 AM, Ben Hutchings wrote:
Use a cgroup.
Is there a compelling reason for me to switch my approach right now,
since I have already solved it another way? If not, I will throw this
on the TODO and investigate post-release. I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/25/2013 10:25 AM, Ben Hutchings wrote:
The reason is, the kernel can make this much easier for you!
I agree I want things to be easier. :)
(That said, I don't know how you're supposed to create a simple
cgroup in a shell script. cgexec
On 03/19/2013 01:23 PM, Daniel Baumann wrote:
ok, so the bug isn't in the runtime configuration (live-config) but in
fglrx doesn't work with kms which we'll need to workaround in the
buildtime configuration (live-images) by conditionally adding nomodeset
to bootappend in case non-free was
Package: debian-installer-launcher
Version: 14
Severity: normal
Steps to reproduce:
Boot
http://live.debian.net/cdimage/release/next/i386/iso-hybrid/debian-wheezy-live-rc1-i386-lxde-desktop.iso
Download and install debian-installer-launcher 14, as this image only
contains 13 which does not
On 04/03/13 06:20 AM, Praveen A wrote:
package: live-installer
version: 40
severity: critical
I downloaded debian-wheezy-live-rc1-amd64-gnome-desktop.iso and live
installer just hangs when selecting Install Debian Sid from System
Tools menu as seen in the screenshot. It was working in
Praveen,
What this comes down to is the b4 version of the image was inadvertently
built with extra material from sid due to an error in configuration (it
was intended that only the live-* packages be included from sid). This
problem was fixed in rc1, but that meant that it used all wheezy
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package debian-installer-launcher
We forgot to include the new debian-installer-launcher in our list of unblocks
for live-*, so our recent build of wheezy live rc1 regressed
On 02/24/2013 04:46 PM, Adam D. Barratt wrote:
Even as a filtered diff, that's still a reasonably large set of
changes. :-(
Sorry about that.
A few comments / queries:
--- live-tools.orig/bin/live-persistence 1970-01-01 01:00:00.0
+0100
+++ live-tools/bin/live-persistence
+
+ [ Daniel Baumann ]
+ * Updating file paths for /lib/live/mount.
+ * Renaming /lib/live/mount/image to /lib/live/mount/medium.
+ * Updating package description.
+ * Adding note about wrappers that replace existing commands in live-
+tools manpage, thanks to Ben Armstrong
+sy
On 11/01/13 07:40 AM, Daniel Baumann wrote:
severity 697873 normal
thanks
On 01/10/2013 10:24 AM, Mike Gach wrote:
[...] with the file name 'persistence'. If I use persistence-label=xyz
and make a file named 'persistence-xyz' [...] when the system is
rebooted, the system will not be using
On 11/01/13 09:44 AM, Daniel Baumann wrote:
On 01/11/2013 02:21 PM, Ben Armstrong wrote:
The man page says that it is a suffix. If the doc is wrong, please fix
the doc to match reality.
which is well know, several times already discussed (with you too :),
and on the wheezy todo.
I know
On 01/03/2013 02:16 PM, Alexey Eromenko wrote:
On Thu, Jan 3, 2013 at 8:05 PM, Didier 'OdyX' Raboud o...@debian.org wrote:
release and lsb-base being Architecture: foreign). Patches are welcome to
make
Wheezy+1 more suitable to your needs.
How about changing it from a kernel bug to
On 01/01/13 07:41 PM, Eugenio 'g7' Paolantonio wrote:
The same script is poking dpkg-internal paths several lines before to
check for the xserver-xorg package.
The vboxvideo driver is contained into the virtualbox-guest-x11 package.
Xorg does not do its driver-selection job because the
On 01/01/13 08:24 PM, Eugenio 'g7' Paolantonio wrote:
The autodetecting mentioned into the live-config man page refers to
the xserver-xorg script and not Xorg itself.
OK. Got it now.
If the xorg-driver boot parameter is blank, the script tries to detect
the driver by looking at the PCI ID of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31/12/12 11:28 AM, David Prévot wrote:
Is there any news from upstream?
Regards
Yes. They immediately released a new point release with license text
fixed by removing cover texts. I just haven't had time to deal with
it. (NMU would be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31/12/12 12:55 PM, David Prévot wrote:
tags 695777 + patch thanks
Dear maintainer,
I've prepared an NMU for gtypist (versioned as 2.9.1-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I should
delay it longer.
Thanks.
On 28/12/12 09:06 AM, Samuel Thibault wrote:
Along the same line, it was suggested on #debian-boot that the main
http://www.debian.org/index page should do the same: CD ISO images
should be before CD vendors in the Getting Debian list.
Also, network install could be more useful to put early.
On 28/12/12 09:08 AM, Samuel Thibault wrote:
I forgot another important thing: I had not even *seen* the Download
Debian 6.0 image on the top-right corner of http://www.debian.org/index
. This is indeed not a place where the eyes would naturally go, so it
tends to be completely unnoticed.
On 28/12/12 11:02 AM, Fernando Toledo wrote:
hello!
i use 3.0~a51-1
i try to make a i386 image from amd64 machine boot running wheezy
any workaround to this?
Perhaps you overlooked in the full bug report that it is fixed in
3.0~b4-1? Simply use that version.
Ben
--
To UNSUBSCRIBE,
Local DNS issues. Resending ...
On 12/20/2012 08:29 AM, Ben Armstrong wrote:
On 12/19/2012 03:38 PM, Adam D. Barratt wrote:
Apologies for letting this slip; what's the current status?
To avoid rework, we need to settle on some final changes that themselves
will cause even more jitter. See
On 15/12/12 07:51 PM, Jakub Wilk wrote:
* Ben Armstrong sy...@sanctuary.nslug.ns.ca, 2012-12-15, 16:15:
In light of this policy, doesn't this mean gtypist is OK? Permission
appears to be already granted to remove those cover texts:
http://lists.debian.org/debian-devel/2012/12/msg00200.html
On 12/12/12 01:35 PM, Jakub Wilk wrote:
I was initially confused by the wording of GR, too. I'll steal the
explanation from http://lists.debian.org/85ac4crw7r@lola.goethe.zz:
The text here differentiates between invariant sections and Invariant
Sections, seemingly calling the Cover Texts
On 12/12/2012 12:38 PM, Jakub Wilk wrote:
Source: gtypist
Version: 2.9.1-2
Severity: serious
Justification: Policy 2.2.1
Usertags: gfdl
doc/gtypist.* has the following license:
| Permission is granted to copy, distribute and/or modify this document
| under the terms of the GNU Free
On 12/12/2012 01:20 PM, Ben Armstrong wrote:
At the same time, we also consider that works licensed under the GNU
Free Documentation License that include no invariant sections do fully
meet the requirements of the Debian Free Software Guidelines.
This means that works that don't include any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/11/12 05:31 AM, Stefano Zacchiroli wrote:
Hi again Ben, any chance you can review and/or apply this patch?
Sorry for bothering again, but I'm about to prepare a related
patch to document how to get Debian on public clouds (bug report
On 11/16/2012 07:27 AM, Michal Suchanek wrote:
When you do squeeze build a squeeze bootstrap is cached. If you do
wheezy build after the bootstrap is restored form cache and upgrade is
run after restore. That may bring the bootstrap up to date to wheezy
version or fail if some dependencies in
On 11/14/2012 04:51 PM, Daniel Baumann wrote:
tag 693242 - patch
thanks
On 11/14/2012 05:02 PM, Thanatermesis wrote:
The apt-get autoclean command removes extra packages in the chroot
but the cache has an incremental and growing size
the current assumption is that the cache of lb is
On 15/11/12 06:38 PM, Michal Suchanek wrote:
You can typically upgrade the bootstrap. There is an upgrade step
anyway in case the bootstrap is stale due to updates to the current
distribution. And it can be cleared manually quite easily.
Please explain how, as I was under the impression
On 02/11/12 04:47 AM, Holger Wansing wrote:
Hi,
Luka Rahne luka.ra...@gmail.com wrote:
Package: installation-reports
Severity: important
-- Package-specific info:
Boot method: usb made with unetbootin from iso
This is suspect. There's no need to do this, as d-i images are isohybrid
and
On 31/10/12 12:42 PM, Frank Gard wrote:
Why are some of the vars named LB_* while others aren't. Bugs like this one
will happen...
I just had a look at this too. Near as I can figure, the ones named LB_
are considered options of live-build itself, whereas the other ones
belong to the
New steps to reproduce. In a clean wheezy chroot:
# apt-get install live-tools
Selecting previously unselected package live-tools.
(Reading database ... 9863 files and directories currently installed.)
Unpacking live-tools (from .../live-tools_3.0.3-1_all.deb) ...
Processing triggers for man-db
get things
released. All that matters is to get things to a releasable state.
Regardless of how this bug is marked, I am not satisfied with the state
it is in.
On 10/23/2012 11:27 AM, Ben Armstrong wrote:
New steps to reproduce. In a clean wheezy chroot:
'clean' as in 'no procps installed
On 10/10/12 05:12 PM, Adam D. Barratt wrote:
On Fri, 2012-08-24 at 08:17 -0300, Ben Armstrong wrote:
Please unblock package live-tools
Primarily to fix diversion conflicts. Also includes doc updates and
other fixes needed for the release.
In the meantime, the package is now up to 3.0.12
On 10/10/12 05:21 PM, Adam D. Barratt wrote:
We're now up to 3.0.8, including four uploads within the space of a week
(one for an entirely pointless standards-version tweak). :-(
Would it be possible to have a cleaned up version of the diff that skips
the translation changes and the noise
On 08/09/12 10:24 PM, Luca Falavigna wrote:
I'm not able to reproduce this bug, with or without Invisible toolbar
in fullscreen mode flag set.
Is it still reproducible? If so, which are your host and guest
resolutions? Which action did you perform?
I'm having a hard time reproducing it, too.
On 03/09/12 05:41 PM, Gyuro Lehel wrote:
* What led up to the situation?
Latest update introduces direct dependency to gdm3, and loads of
gnome-related libs.
* What exactly did you do (or not do) that was effective (or
ineffective)?
N/A
* What was the outcome of this action?
On 08/30/2012 12:03 PM, George Bak wrote:
I tried to reproduce this bug again.
Strange, but I cannot reproduce it anymore.
May be aptitude upgrade removed it?
I doubt it. There are so few dependencies of live-build. Most things happen
inside the chroot which
is populated from a debootstrap,
Unreproducible. Unfortunately, since you only excerpted the build.log and
didn't show the whole
thing, we have no way of knowing if there were earlier problems that led to the
failure at the end
that you included in your bug report. Please try a fresh build in a new
directory again, and this
On 25/08/12 07:29 AM, os.n...@gmx.de wrote:
please have a look at bug 655505. I reported the same or similar
bug at 11. January 2012 with the installer. Now I wanted to try out
if the bug is solved.
Sure, no problem with that. But in that case, since you did an actual
install, an
On 24/08/12 01:22 PM, os.n...@gmx.de wrote:
Package: installation-reports
I built the following live iso-hybrid from http://live-build.debian.net:
distribution: wheezy
package-lists: kde
architectures: i386
bootstrap-flavour: standard
linux-flavours: 486
bootappend: locales=de_DE.UTF-8
On 05/07/12 07:52 PM, Colin Watson wrote:
Hi PuTTY team,
This sounds like an interesting thing for somebody to check out :-)
The exact patches I've applied can be found here:
http://anonscm.debian.org/loggerhead/pkg-ssh/putty/trunk/changes
On 23/08/12 08:17 AM, BG - Ben Armstrong wrote:
Any chance to look at this yet? I've had to put my putty on hold, as
the release in wheezy breaks for an important use case for my work.
I would be happy to assist in any way I can.
I can now report that using a local rebuild of the debian
On 23/08/12 09:18 AM, Simon Tatham wrote:
I fixed this upstream as soon as I heard of it, in early July
(r9573). I seem to have forgotten to CC the Debian bug report when I
notified Colin that I'd committed the fix; I apologise if that
caused a delay.
If you're happy to rebuild and test
On 18/08/12 02:59 PM, LeJacq, Jean Pierre wrote:
Package: live-build
Version: 3.0~a57-1
Severity: important
--- Please enter the report below this line. ---
Configuring debian-live using the git rescue configuration and building an
hdd
image, results in an usable system.
Sounds like
On 07/31/2012 05:51 PM, Christian PERRIER wrote:
Committed. Last word, right? :-)
Damn, I sure hope so. :)
Ben
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On 07/30/2012 08:19 PM, Bob Bib wrote:
please don't force the gdm3 dependency;
I have had some discussion this morning with the Debian lxde maintainers and we
agree the gdm3
dependency explosion (a fairly recent thing, looking at gdm3's Debian
changelog) renders it much
less desirable to use
On 07/31/2012 11:42 AM, Ben Armstrong wrote:
While my brief testing of lightdm indicates it is a possible candidate, but
there is also slim to
consider. We're considering the merits of each before requesting a change to
task-lxde-desktop.
We have concluded our testing and discussion
I retested with a simpler config, just the 'standard' list this time,
but otherwise the same as before. Also, I turned on 'set -x' in the init
script in initramfs to see what was happening. It turns out the crash
occurs in the middle of live-bottom scripts, and that's when I began to
suspect
Package: linux-image-3.2.0-3-686-pae
Version: 3.2.21-3
Severity: normal
I built a fresh sid live i386 image using no special customization (just
includes kde-full builtin package list) and 686-pae kernel. I cannot
boot this image on an Atom N450 system due to the following kernel
panic
On 07/07/12 02:18 PM, Antoine Beaupré wrote:
I have tried the install method described here with the Debian Wheezy alpha1
d-i:
http://d-i.alioth.debian.org/manual/en.i386/apas02.html#howto-getting-images-usb
First, this is not the official doc, but is an internal site used to
track
Package: putty
Version: 0.62-8
Severity: normal
In a recent upgrade of putty, application keypad mode keys PF2,
PF3 and PF4 stop working. They generate the symbols for normal
mode instead: /, * and - respectively.
Example use case:
When I press NumLock Keypad-*, which should generate the PF1PF3
Gerben,
On 06/27/2012 07:46 AM, Gerben van Ek wrote:
Package: live-build
Version: 3.0~a50-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I tried to make a new build of a Debian Live image. It fails on trying to
install the smbfs package, which is no longer
Package: wpasupplicant
Version: 1.0-2
Severity: normal
I was excited to see in the changelog that 1.0 adds a 'blacklist BSSID'
command, something I've long wanted for congested areas where I am
accepting connections for any open network with any ESSID, but many
are not free and therefore not
Package: wpasupplicant
Version: 1.0-2
Severity: normal
wpa_cli output can get very verbose. As an aid to seeing only the
changes to the output since I last looked, I am in the habit of using
ctrl-L to clear the screen. However, ever since 1.0, ctrl-L no longer
does this. Nor can I find a command
Package: wpasupplicant
Version: 1.0-2
Severity: normal
Up-arrow skips over the previous line in the command history and shows
the one before that (but only the first time). Steps to reproduce:
help
scan_results
up-arrow
help - help is now shown, whereas scan_results was expected
On 18/06/12 08:46 PM, Stefan Lippers-Hollmann wrote:
I'm lowering the severity to minor, because in my opinion this
doesn't impose a significant impact on wpa_cli's usability.
Sure. As a workaround, I'll just press and hold the enter key
periodically. A bit ugly, but serves the same function.
To clarify what I meant by but only the first time, follow this example:
1
2
3
4
up-arrow
3
up-arrow
2
That is, if you press two consecutive up-arrows, the line before last,
and the line before that are retrieved from the history. The bug only
occurs on the first of the up-arrows.
Ben
Package: calibre
Version: 0.8.41+dfsg-1
Severity: normal
For a short time I had network-manager installed because Gnome3 in sid
could not be installed without it. I configured it, however, to not
manage any of my interfaces because I prefer to use ifupdown. This
caused Calibre some problems: it
On 02/04/12 04:27 PM, recovery...@gmail.com wrote:
At least when using ASUS x101h eeepc, synclient doesn't actually do anything
as it fails with:
$ synclient -l
Couldn't find synaptics properties. No synaptics driver loaded?
Could you also please provide any kernel messages relating to your
On 03/20/2012 05:11 PM, Ivan Krylov wrote:
Package: wnpp
Severity: wishlist
Owner: Ivan Krylovkrylov.r...@gmail.com
* Package name: sandbox
I worry about how generic this name is. I know of at least
'sandboxgamemaker' package (Platinum Arts Sandbox) which was renamed to
avoid conflicts.
101 - 200 of 479 matches
Mail list logo
