pkgdetails and ar as a shell script
Not sure if there's any use for it upstream, but I figure I might as well alert you all to an adaption of debootstrap's pkgdetails [1] and the extract functionality of ar [2] into posix shell. The ar adaption is dead simple; I'm surprised nobody has done it before (or maybe they have, and my cursory searches didn't turn it up). The pkgdetails adaption was less simple, and while it works (and of course produces the same output as the C and Perl versions, as far as I can tell), it's definitely slower than the other two. These scripts work well for running debootstrap in a standard Chromium OS environment (no Perl, Python, or build tools), so perhaps the Debian community could find something useful to do with them as well. -David [1] https://github.com/dnschneid/crouton/blob/master/installer/pkgdetails [2] https://github.com/dnschneid/crouton/blob/master/installer/ar
Bug#686502: pxz produces archives broken for busybox's unxz
On Sun, 2013-01-06 at 23:32 +0100, Bastian Blank wrote:
On Thu, Dec 27, 2012 at 10:08:07PM +0100, Abou Al Montacir wrote:
+ if (r == XZ_STREAM_END) {
+ /* Eat padding. Stream never starts with zeros, and
padding is 32 aligned */
+ while ((iobuf.in_pos iobuf.in_size)
(iobuf.in[iobuf.in_pos] == 0)) {
+ iobuf.in_pos += 1;
+ }
+ /* Reached end of buffer. Fill it again from stream */
+ if (iobuf.in_pos == iobuf.in_size) {
+ continue;
+ }
+ if(iobuf.in_pos % 4){
Are you sure this is correct? in_pos is the position in tht buffer, not
the file. Also look out for coding style.
Provided the buffer size is multiple of 4 bytes, which is the case for
BUFSIZ. Of course one can decide to use a mis aligned buffer, but this
is not common and I consider it bad coding practice.
+ if (r == XZ_STREAM_END) {
Again the same check?
Not really, r could have been changed since the above check (r = XZ_DATA_ERROR;
when %4 check fails)
if (r == XZ_STREAM_END) {
- break;
+ xz_dec_end(state);
+ /* Look for any other streams */
+ continue;
Why do you have three XZ_STREAM_END checks in this state machine?
I use XZ_STREAM_END to check end of stream and eat padding, to check
there is still valid data (no paddding error) before initializing
decoder, and finally to free the decoder at en of current stream.
Cheers,
signature.asc
Description: This is a digitally signed message part
Bug#697331: installation-reports: Printer not working / recognised - Fixed
On Sun 06 Jan 2013 at 06:53:46 +0100, Christian PERRIER wrote: Quoting de28jihem (de28ji...@scarlet.be): The user was not in lpadmin group (checked with id). This caused problem to use the CUPS configuration menu (localhost:631). Added the user in lpadmin (under root) : usermod -a -G lpadmin user1 Plugged in printer/scan. Started a web browser, url localhost:631 (the CUPS interface) Select the admin tab; add printer; ... (almost all fields already filled in) Printing ok (from mousepad editor libre office document) H, that brings the problem back in the scope of the installer, then. The initial group membership *for the first created user* is done in D-I (though the user-setup module) and the user is added to a predefined set of useful groups. Your experience brings the question of whether we should add lpadmin to this. However, I don't understand why one should be a member of lpadmin in order to *print*. The problem encountered by de28jihem in setting up and administering a print queue is not uncommon; #680195 gives another example. The list of useful groups in passwd/user-default-groups has scanner and debian-tor, both of which were added in recent times without any fuss or controversy. There may be arguments against adding the first created user to the lpadmin group but, at first sight, it appears to be at least as beneficial as any of the existing default groups, especially as the choice of installed tasks now includes a print server. Regards, Brian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130107132218.GA21426@desktop
Processed: reassign 697035 to src:linux
Processing commands for cont...@bugs.debian.org: reassign 697035 src:linux 3.2.35-2 Bug #697035 [installation-reports] installer: kb and mouse don't work on a decTop (NSC geode processor) Bug reassigned from package 'installation-reports' to 'src:linux'. Ignoring request to alter found versions of bug #697035 to the same values previously set Ignoring request to alter fixed versions of bug #697035 to the same values previously set Bug #697035 [src:linux] installer: kb and mouse don't work on a decTop (NSC geode processor) Marked as found in versions linux/3.2.35-2. thanks Stopping processing here. Please contact me if you need assistance. -- 697035: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697035 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.135756709619212.transcr...@bugs.debian.org
Bug#681227: Can anyone reproduce #681227: installation-reports: grub-install tries to install to a nonsense string?!
Hi, Sorry, I don't think this email's going to help very much. On 02/01/13 22:49, Steven Chamberlain wrote: Hi! On 02/01/13 20:26, Cyril Brulebois wrote: Jul 10 16:48:43 in-target: grub-common is already the newest version. Jul 10 16:48:43 in-target: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Jul 11 07:56:28 grub-installer: info: Installing grub on '/dev/sdb w33sxs34rfvbg789iokm·']' Notice the long delay there. I suspect the installer paused at `db_get grub-installer/bootdev`, which according to grub-installer.templates for v1.70 was of 'string' type: Template: grub-installer/bootdev Type: string The device should be specified as a device in /dev. Below are some examples: So I imagined typing that 'nonsense' string on a keyboard: w33... sxs... 34rfvbg... 789iokm... and a middot which I'm not sure how you would type, and finally ... ']... enter key? On a QWERTY keyboard these sequences of keys are all adjacent! To the original submitter of the bug report: do you have a cat? No. The machine is my work desktop. I do have a QWERTY keyboard (Microsoft Natural Ergonomic Keyboard 4000). I don't know how one might have gotten a middot out of it! That said, I cannot eliminate the possibility that a cleaner was overzealous or similar, but it seems unlikely...? Regards, Matthew -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50eb02af.3090...@coriolis.greenend.org.uk
Re: Bug#681227: Can anyone reproduce #681227: installation-reports: grub-install tries to install to a nonsense string?!
Hi Matthew, On 07/01/13 17:15, Matthew Vernon wrote: Jul 10 16:48:43 in-target: grub-common is already the newest version. Jul 10 16:48:43 in-target: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Jul 11 07:56:28 grub-installer: info: Installing grub on '/dev/sdb w33sxs34rfvbg789iokm·']' On 02/01/13 22:49, Steven Chamberlain wrote: To the original submitter of the bug report: do you have a cat? No. The machine is my work desktop. I do have a QWERTY keyboard [...] I don't know how one might have gotten a middot out of it! I've just learned that at least with my keyboard layout (gb), AltGr + period will type the interpunct/middot, in Xorg or from a Linux terminal. Those keys are more or less adjacent too. That said, I cannot eliminate the possibility that a cleaner was overzealous or similar, but it seems unlikely...? I'm convinced this is the explanation. The installer was stuck at a GRUB prompt for boot devices overnight; then at 07:56 (usually 'accurate', but might not be in the local timezone) GRUB proceeded trying to install to: w33 sxs 34rfvbg ... 789iokm ·'] This seems to fit with down/up sweeps across a QWERTY keyboard with one's cleaning cloth, proceeding from the left to right (so I would even guess that he/she is right-handed...). [The split on an ergo keyboard would be between the ...vbg and 789... sequences of keystrokes, and the closing square bracket is adjacent to the carriage return key]. So I think this can be closed. What to do with the workaround added by Wouter in grub-installer/1.84? It did trigger a couple of regressions initially, but those are fixed now in Git. Silently ignoring a failure seems risky when we know that it should not happen. (Someone may want to specify multiple targets, and if one of them is typo'd it would be silently skipped in this case). So I think it might be best to revert it? Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50eb0bbb.9020...@pyro.eu.org
Bug#697331: installation-reports: Printer not working / recognised - Fixed
reassign 697331 user-setup retitle 697331 Please add the first created user to lpadmin thanks Quoting Brian Potkin (claremont...@gmail.com): The problem encountered by de28jihem in setting up and administering a print queue is not uncommon; #680195 gives another example. The list of useful groups in passwd/user-default-groups has scanner and debian-tor, both of which were added in recent times without any fuss or controversy. There may be arguments against adding the first created user to the lpadmin group but, at first sight, it appears to be at least as beneficial as any of the existing default groups, especially as the choice of installed tasks now includes a print server. Convincing. So I'm reassigning this bug where it pertains. Maybe #680195 should be mergedwith it if it's the same problem (no easy way check right now). signature.asc Description: Digital signature
Processed: Re: Bug#697331: installation-reports: Printer not working / recognised - Fixed
Processing commands for cont...@bugs.debian.org:
reassign 697331 user-setup
Bug #697331 {Done: Christian PERRIER bubu...@debian.org}
[installation-reports] installation-reports: Printer not working / recognised
Bug reassigned from package 'installation-reports' to 'user-setup'.
Ignoring request to alter found versions of bug #697331 to the same values
previously set
Ignoring request to alter fixed versions of bug #697331 to the same values
previously set
retitle 697331 Please add the first created user to lpadmin
Bug #697331 {Done: Christian PERRIER bubu...@debian.org} [user-setup]
installation-reports: Printer not working / recognised
Changed Bug title to 'Please add the first created user to lpadmin' from
'installation-reports: Printer not working / recognised'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
697331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.135758511022126.transcr...@bugs.debian.org
Re: Bug#681227: Can anyone reproduce #681227: installation-reports: grub-install tries to install to a nonsense string?!
retitle 681227 does not validate free-form input thanks On Mon, Jan 07, 2013 at 05:54:03PM +, Steven Chamberlain wrote: Hi Matthew, On 07/01/13 17:15, Matthew Vernon wrote: Jul 10 16:48:43 in-target: grub-common is already the newest version. Jul 10 16:48:43 in-target: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Jul 11 07:56:28 grub-installer: info: Installing grub on '/dev/sdb w33sxs34rfvbg789iokm·']' On 02/01/13 22:49, Steven Chamberlain wrote: To the original submitter of the bug report: do you have a cat? No. The machine is my work desktop. I do have a QWERTY keyboard [...] I don't know how one might have gotten a middot out of it! I've just learned that at least with my keyboard layout (gb), AltGr + period will type the interpunct/middot, in Xorg or from a Linux terminal. Those keys are more or less adjacent too. That said, I cannot eliminate the possibility that a cleaner was overzealous or similar, but it seems unlikely...? I'm convinced this is the explanation. The installer was stuck at a GRUB prompt for boot devices overnight; then at 07:56 (usually 'accurate', but might not be in the local timezone) GRUB proceeded trying to install to: w33 sxs 34rfvbg ... 789iokm ·'] This seems to fit with down/up sweeps across a QWERTY keyboard with one's cleaning cloth, proceeding from the left to right (so I would even guess that he/she is right-handed...). [The split on an ergo keyboard would be between the ...vbg and 789... sequences of keystrokes, and the closing square bracket is adjacent to the carriage return key]. So I think this can be closed. Almost. What to do with the workaround added by Wouter in grub-installer/1.84? The workaround tried to eliminate the possibility of invalid data coming from somewhere in the installer. I hadn't noticed the long delay in the log; I had noticed the possibility of invalid input, but didn't think you'd be silly enough to enter such a long string and not notice. Of course, if the installer was running overnight, that changes matters. So what I think needs to be done to fix this properly is to move the check from where it is located right now to where we do the db_get for the installer device. If what's been entered by the user doesn't look like a hard disk device, we should display an error message and allow the user to try again. However, given we're this late in the freeze, and given that we've already got the workaround in place (which should allow a retry by going through the main menu), I'm not sure it's appropriate anymore to do this right now. I'll leave that decision to the d-i RM. It did trigger a couple of regressions initially, but those are fixed now in Git. Silently ignoring a failure seems risky when we know that it should not happen. (Someone may want to specify multiple targets, and if one of them is typo'd it would be silently skipped in this case). That's indeed the only case that isn't caught by the current code. Still, first, this is a highly unusual installation type; and second, even were it to occur, an easy workaround is to use the installer in rescue mode and fix the boot set-up -- or fix it from the installed system. Again, it's not a perfect situation, but I'm not sure this is RC anymore. -- Copyshops should do vouchers. So that next time some bureaucracy requires you to mail a form in triplicate, you can mail it just once, add a voucher, and save on postage. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130107195616.ga21...@grep.be
Processed: Re: Bug#681227: Can anyone reproduce #681227: installation-reports: grub-install tries to install to a nonsense string?!
Processing commands for cont...@bugs.debian.org: retitle 681227 does not validate free-form input Bug #681227 [grub-installer] installation-reports: grub-install tries to install to a nonsense string Changed Bug title to 'does not validate free-form input' from 'installation-reports: grub-install tries to install to a nonsense string' thanks Stopping processing here. Please contact me if you need assistance. -- 681227: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681227 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13575960062323.transcr...@bugs.debian.org
Bug#697331: installation-reports: Printer not working / recognised - Fixed
Clarification : Adding user1 to the lpadmin group was required to add the printer in CUPS (otherwise after entering the user name and password the operation is forbidden), not for printing. Test : remove user1 from lpadmin print root? root? id user1 uid=1000(user1) gid=1000(user1) groupes=1000(user1),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),103(scanner),106(netdev),113(lpadmin) root? deluser user1 lpadmin Suppression de l'utilisateur « user1 » du groupe « lpadmin »... Fait. root? id user1 uid=1000(user1) gid=1000(user1) groupes=1000(user1),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),103(scanner),106(netdev) and I still can print (from libreoffice writer) But still puzzling is the fact that the BX300F was usable plug n'print/scan in squeeze-custom-amd64-0315.iso (gnome version; downloaded from http://kmuto.jp/debian/d-i/ ). I had no need to get into CUPS to add the printer, and anyway I would have had the same forbidden problem to access CUPS as the user is not in lpadmin group ! I tested it on that version. Log from squeeze-custom-amd64-0315 : root? id user1 uid=1000(user1) gid=1000(user1) groupes=1000(user1),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),109(netdev),110(bluetooth),116(scanner) and no way to add a printer using CUPS ! (forbidden) So, adding the user in lpadmin would be a workaround for a manual installation of the printer, not really a plug n'print solution. More info : squeeze-custom-gnome uses HAL wheezy-xfce uses UDEV I found some similar/related problem on https://bugs.launchpad.net/ubuntu/+source/xfprint4/+bug/472656 but is is (should be) fixed in xfprint4 (4.6.1-3) which is currently installed. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130107234153.07d91a4c93cd8c350dd06...@mobistarmail.be
Bug#697331: installation-reports: Printer not working / recognised - Fixed
Quoting jswmb01x (jswmb...@mobistarmail.be): Clarification : Adding user1 to the lpadmin group was required to add the printer in CUPS (otherwise after entering the user name and password the operation is forbidden), not for printing. Hmmm, well, then I would say this is cups that changed its behaviour and made it a requirement to have privleges in order to add a printer, even plug n' play toys. Which makes sense to me. Indeed, even on Windows, unprivileged users cannot add local printers to the system (but most Windows users don't notice as they always virtually work as root on their machines). That makes it less of a requirement to have the first created user in lpadmin, after more thinking. This bug could then even be wontfix. signature.asc Description: Digital signature
Bug#697331: installation-reports: Printer not working / recognised - Fixed
On Tue, Jan 08, 2013 at 07:14:26AM +0100, Christian PERRIER wrote: Quoting jswmb01x (jswmb...@mobistarmail.be): Clarification : Adding user1 to the lpadmin group was required to add the printer in CUPS (otherwise after entering the user name and password the operation is forbidden), not for printing. Hmmm, well, then I would say this is cups that changed its behaviour and made it a requirement to have privleges in order to add a printer, even plug n' play toys. Which makes sense to me. Indeed, even on Windows, unprivileged users cannot add local printers to the system (but most Windows users don't notice as they always virtually work as root on their machines). That makes it less of a requirement to have the first created user in lpadmin, after more thinking. This bug could then even be wontfix. I don't understand your reasoning. We also add the user to sudo if no root password is set. And to netdev for the administration of network devices. Along the same lines the user should be added to lpadmin. What annoys me more is that it seems to be inflationary to add new default groups, like debian-tor. I've got nothing against TOR, but filesystems like NFSv3 are limited to 16 groups to be transmitted with a request. If a user has more groups, the others are dropped. Hence we should be somewhat careful how many different groups we introduce, especially by default. |: Kind regards Philipp Kern signature.asc Description: Digital signature
Re: Adding armhf vexpress udebs
On Wed, Jan 02, 2013 at 08:56:45PM +0100, Cyril Brulebois wrote: Cyril Brulebois k...@debian.org (24/11/2012): From a d-i point of view, this is more than welcome. I haven't reviewed the patch itself yet, but you can commit it right now, as d-i wheezy beta 4 has just been released. Just remember to keep us posted if some issues are detected in the upcoming days, so that we don't release d-i wheezy rc1 with a buggy vexpress support. ;-) Aurélien, ping? Sorry about doing that late and also for the late answer. The changes have been committed to the linux SVN on December 31st. -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130107232858.gb4...@ohm.aurel32.net
Re: Adding armhf vexpress udebs
Hello, Aurelien Jarno aurel...@aurel32.net (08/01/2013): On Wed, Jan 02, 2013 at 08:56:45PM +0100, Cyril Brulebois wrote: Cyril Brulebois k...@debian.org (24/11/2012): From a d-i point of view, this is more than welcome. I haven't reviewed the patch itself yet, but you can commit it right now, as d-i wheezy beta 4 has just been released. Just remember to keep us posted if some issues are detected in the upcoming days, so that we don't release d-i wheezy rc1 with a buggy vexpress support. ;-) Aurélien, ping? Sorry about doing that late and also for the late answer. The changes have been committed to the linux SVN on December 31st. no worries, we're not entirely ready yet anyway; thanks for the heads-up! Mraw, KiBi. signature.asc Description: Digital signature
