Re: [arch-general] Invalid signatures
On Tue, 06 Nov 2012 20:33:20 +0100 Thomas Bächler wrote: > Am 06.11.2012 20:11, schrieb Leonid Isaev: > > A bit OT, but anyway... Are there any plans for actually storing *.sig > > files in the cache alongside the packages? This costs a tiny amount of > > space, but IMHO will make verification (especially of old packages) much > > easier. > > pacman does not download them, so it cannot store them. > > Signatures are contained in the db file. > > Yes, but it's only for the current (latest synced) set of packages, and even then I have to parse the desc files and filter the ascii sigs through base64, all outside of pacman which I think does it anyway at the verification stage. Hence my question. For example, I don't mind a performance hit due to regeneration of all binary signatures on the fly. Just an opinion though... -- Leonid Isaev GnuPG key: 0x164B5A6D Fingerprint: C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D signature.asc Description: PGP signature
Re: [arch-general] Invalid signatures
On Tue, Nov 06, 2012 at 01:11:38PM -0600, Leonid Isaev wrote: > On Tue, 6 Nov 2012 14:02:23 -0500 > Dave Reisner wrote: > > > On Tue, Nov 06, 2012 at 01:50:01PM -0500, David Rosenstrauch wrote: > > > Saw these errors from pacman today, which are preventing me from > > > upgrading some packages: > > > > > > error: directfb: signature from "Eric Belanger " > > > is invalid > > > error: xmms2: signature from "Sergej Pupykin " is > > > invalid error: failed to commit transaction (invalid or corrupted package > > > (PGP signature)) > > > > > > Anyone have an idea what's up? > > > > > > DR > > > > Nuke the packages from your cache, and redownload them. The error > > message is misleading -- the signatures are invalid FOR the packages, > > meaning the package data is not what the signature "expected". > > > > The situation is much improved come pacman 4.1 -- we'll just prompt you > > to delete the package, much like we did historically when a package > > failed checksums. > > > > d > > A bit OT, but anyway... Are there any plans for actually storing *.sig files > in the cache alongside the packages? This costs a tiny amount of space, but > IMHO will make verification (especially of old packages) much easier. We don't have any plans right now to do this. d
Re: [arch-general] Invalid signatures
Am 06.11.2012 20:11, schrieb Leonid Isaev: > A bit OT, but anyway... Are there any plans for actually storing *.sig files > in the cache alongside the packages? This costs a tiny amount of space, but > IMHO will make verification (especially of old packages) much easier. pacman does not download them, so it cannot store them. Signatures are contained in the db file. signature.asc Description: OpenPGP digital signature
Re: [arch-general] Invalid signatures
On Tue, Nov 6, 2012 at 7:50 PM, David Rosenstrauch wrote: > Saw these errors from pacman today, which are preventing me from upgrading > some packages: > > error: directfb: signature from "Eric Belanger " is > invalid > error: xmms2: signature from "Sergej Pupykin " is invalid > error: failed to commit transaction (invalid or corrupted package (PGP > signature)) > > Anyone have an idea what's up? > > DR Try https://wiki.archlinux.org/index.php/Pacman#Q:_I_keep_getting_a_.22failed_to_commit_transaction_.28invalid_or_corrupted_package.29.22_error (next to last question)
Re: [arch-general] Invalid signatures
On Tue, 6 Nov 2012 14:02:23 -0500 Dave Reisner wrote: > On Tue, Nov 06, 2012 at 01:50:01PM -0500, David Rosenstrauch wrote: > > Saw these errors from pacman today, which are preventing me from > > upgrading some packages: > > > > error: directfb: signature from "Eric Belanger " > > is invalid > > error: xmms2: signature from "Sergej Pupykin " is > > invalid error: failed to commit transaction (invalid or corrupted package > > (PGP signature)) > > > > Anyone have an idea what's up? > > > > DR > > Nuke the packages from your cache, and redownload them. The error > message is misleading -- the signatures are invalid FOR the packages, > meaning the package data is not what the signature "expected". > > The situation is much improved come pacman 4.1 -- we'll just prompt you > to delete the package, much like we did historically when a package > failed checksums. > > d A bit OT, but anyway... Are there any plans for actually storing *.sig files in the cache alongside the packages? This costs a tiny amount of space, but IMHO will make verification (especially of old packages) much easier. -- Leonid Isaev GnuPG key: 0x164B5A6D Fingerprint: C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D signature.asc Description: PGP signature
Re: [arch-general] Invalid signatures
On Tue, Nov 06, 2012 at 01:50:01PM -0500, David Rosenstrauch wrote: > Saw these errors from pacman today, which are preventing me from > upgrading some packages: > > error: directfb: signature from "Eric Belanger " > is invalid > error: xmms2: signature from "Sergej Pupykin " is invalid > error: failed to commit transaction (invalid or corrupted package > (PGP signature)) > > Anyone have an idea what's up? > > DR Nuke the packages from your cache, and redownload them. The error message is misleading -- the signatures are invalid FOR the packages, meaning the package data is not what the signature "expected". The situation is much improved come pacman 4.1 -- we'll just prompt you to delete the package, much like we did historically when a package failed checksums. d
[arch-general] Invalid signatures
Saw these errors from pacman today, which are preventing me from upgrading some packages: error: directfb: signature from "Eric Belanger " is invalid error: xmms2: signature from "Sergej Pupykin " is invalid error: failed to commit transaction (invalid or corrupted package (PGP signature)) Anyone have an idea what's up? DR
[arch-general] Qingy on systemd
I recently switched over to systemd, and am trying to get my system set up the way I like under there. I'm trying to set up qingy on systemd right now, but it doesn't seem to be working properly. I followed the instructions here: https://wiki.archlinux.org/index.php/Qingy#Systemd ... and tried to set up qingy on tty6. But that doesn't seem to work. The systemctl command seems to always try to set up qingy on tty1: [darose@daroselin ~]$ sudo systemctl enable qingy@tty6 ln -s '/usr/lib/systemd/system/qingy@.service' '/etc/systemd/system/getty.target.wants/qingy@tty1.service' In addition, qingy seems to be freezing on me whenever I try to access it on the tty. Anyone have any idea what's going on with this? I didn't see any bug reports about it. Thanks, DR
Re: [arch-general] gstreamer vs gstreamer0.10
1.0 has a slightly different API, is missing some plugins and has gained others. Otherwise they're pretty much equivalent. If building packages, build against GStreamer 1.0, if possible. 0.10 is deprecated. On Mon, Nov 5, 2012 at 8:10 PM, DG wrote: > Quick question on the 2 gstreamer packages currently in extra (gstreamer & > gstreamer0.10) - is one "preferred" over the other? It looks like > gstreamer is v1.0 and is used by gnome3, so is gstreamer0.10 being > transitioned out? Do they provide the same functionality? > > Thanks, > Danny G
Re: [arch-general] Forking daemons and systemd
Am 06.11.2012 02:22, schrieb ianux: > Is it safe to assume that if a daemon is meant to be run in > foreground (i.e default behaviour, without options) , it is safe to run > it this way in the corresponding service file ? I'd say yes. In practice, you should just try it, and if any bugs appear see if Type=simple is the problem. signature.asc Description: OpenPGP digital signature
Re: [arch-general] Systemd and inactive sessions
Am 05.11.2012 22:43, schrieb Leonid Isaev: >> Important caveat to that setting: >> >> "Note that setting KillUserProcesses=1 will break tools like screen(1)" >> >> DR >> > > Yes, I learnt that the hard way :) So it's a useful setting for a laptop, but > obviously not for a server... I was hoping to be able to fix that. In theory, we could teach screen to open a PAM session and teach logind to respect screen as a session master - but I really don't know where to start. signature.asc Description: OpenPGP digital signature
Re: [arch-general] USB Flash drive problems
On Sun, 4 Nov 2012 18:58:09 + "P .NIKOLIC" wrote: > Hi . > > Just purchased several SanDisk 4Gb Cruzer Blade USB flash drives but > can not access any of them . the only error report i can find just > says > An error occurred while accessing `3.7GiB Removable Media`, the system > responded: An unspecified error has occurred.: Not Authorized > > This happens both as user or root , any other non SanDisk flash drive > is fine . I was hoping to put music on them for the car as the system > incar can only read 4 Gb Max drives these seemed ideal look like they > may bee a bummer . > > Any tips anyone .. > > > Pete . > > > -- > Linux 7-of-9 3.6.4-1-ARCH #1 SMP PREEMPT Mon Oct 29 09:49:00 CET 2012 > x86_64 GNU/Linux When this happened to me, I did the following to fix it... # pacman -S ntfs-3g -- Todd Carnes
Re: [arch-general] USB Flash drive problems
On Mon, Nov 05, 2012 at 07:00:43PM +, P .NIKOLIC wrote: > On Mon, 5 Nov 2012 17:18:48 +0200 > Tom Rand wrote: > > > My son-in-law recently purchased 2 of these & he could not access > > them on PS3 or my arch desktop. > > It turned out they were formatted as EXFAT, he re-formatted as NTFS & > > all was ok for him. > > > > What are yours formatted as? > > > > Also I have had similar issue's in the past & just re-formatted to > > FAT & all was ok. > > > Hi Tom . > > Been there using the laptop that is not as upto date and completely > redid the partition and formatted one of them vfat still the same on > this machine but ok on the laptop . > > I need to keep them vfat as they are actually for use in the car it > takes mp3's on usb drives (max 4Gb) and only read vfat (and only mp3 > not ogg) > > Pete . > > > > > -- > Linux 7-of-9 3.6.5-1-ARCH #1 SMP PREEMPT Wed Oct 31 20:57:39 CET 2012 > x86_64 GNU/Linux I take it you tried all ports on this machine. (apologies for the top post earlier) the only other possible thing i could think of which might cause this would be that your mobo is set to use usb 3 only or one of the other versions I know some mobo's can be set to one of the 3. Either that or some of the ports are not initialised. plug the drive in run lsusb this at least will tell you if the drive is visible &/or if the usb port is initialised.
Re: [arch-general] USB Flash drive problems
On Mon, 5 Nov 2012 15:03:52 -0500 Dave Reisner wrote: > On Mon, Nov 05, 2012 at 08:22:33PM +0100, coderkun wrote: > > Am Montag, den 05.11.2012, 18:22 + schrieb P .NIKOLIC: > > > How do i check to see if it is systemd or not > > > > $ printf "%d" `systemd-notify --booted` > > systemd-notify doesn't print anything. If you really want to print > something: > > $ systemd-notify --booted && echo "booted on systemd" > > or > > $ systemd-notify --booted; echo $? > > > > > man systemd-notify: > > “[…] > > --booted > > Returns 0 if the system was booted up with systemd, non-zero > > otherwise. […]” > > > > Note the "returns", not "prints". > > d Hi All .. Well after a little messing now on systemd , And the strange thing is that now ALL the usb flash drives i have work not just the older ones but the new SanDisk as well Explain that one someone . I think this can be classed as solved right now thanks all Pete . -- Linux 7-of-9 3.6.5-1-ARCH #1 SMP PREEMPT Wed Oct 31 20:57:39 CET 2012 x86_64 GNU/Linux
Re: [arch-general] USB Flash drive problems (SOLVED)
On Mon, 5 Nov 2012 19:00:43 + "P .NIKOLIC" wrote: > On Mon, 5 Nov 2012 17:18:48 +0200 > Tom Rand wrote: > > > My son-in-law recently purchased 2 of these & he could not access > > them on PS3 or my arch desktop. > > It turned out they were formatted as EXFAT, he re-formatted as NTFS > > & all was ok for him. > > > > What are yours formatted as? > > > > Also I have had similar issue's in the past & just re-formatted to > > FAT & all was ok. > > > Hi Tom . > > Been there using the laptop that is not as upto date and completely > redid the partition and formatted one of them vfat still the same on > this machine but ok on the laptop . > > I need to keep them vfat as they are actually for use in the car it > takes mp3's on usb drives (max 4Gb) and only read vfat (and only mp3 > not ogg) > > Pete . > > > > Replying to ones self .. as in the previous mail Now Solved Pete -- Linux 7-of-9 3.6.5-1-ARCH #1 SMP PREEMPT Wed Oct 31 20:57:39 CET 2012 x86_64 GNU/Linux
Re: [arch-general] resume do not work after self suspend in gnome 3.6
> > > Hi Mathieu, what's your video card? $ lspci | grep -i vga will do it. 0:41 mathieu@kubrick ~ % lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) > Also: > 1. do you have installed acpi, no > laptop-mode-tools no. > or pm-utils? yes, required bu upower, required by gdm Do you think i need to install them ? (it worked well without them until gnome 3.6) > 2. what does happen if you suspend your system using the pm-suspend > tool? it wake up correctly (without locking screen) > A $ man pm-suspend will give you useful data about the quirks flags > you can use. my problem is not to suspend the laptop, only wake up when have been suspending by gnome cause idling. -- Mathieu R. http://400iso.net/
Re: [arch-general] Forking daemons and systemd
Le 05/11/12, Dave Reisner a écrit : > On Mon, Nov 05, 2012 at 10:01:11AM -0600, Leonid Isaev wrote: > > Hi, > > > > I was wondering whether there is a guideline regarding using > > Type=forking daemons in systemd units. For instance, if a daemon > > supports a cmdline switch to run in foreground isn't it better to > > use this argument in ExecStart? > > Personally, I was bitten by this with haveged.service which > > fails on shutdown and whose unit has Type=forking, but I also > > noticed that ntpd is allowed to fork. Both of them support > > foreground operation (haveged -F and ntpd -n respectively)? > > Essentially, it comes down to ordering of other daemons. > > It's always going to be some trifling amount faster to start a daemon > in the foreground because systemd assumes it to be alive as soon as it > starts. Conversely, a Type=forking daemon is only considered alive > only once the parent process has exited. > > What this means is that while you might be able to start a daemon > which normally forks in non-forking mode, you can't guarantee that > daemons which rely on the non-forking daemon can be reliably started, > since various listeners or other channels may not be established in > time. > > The ideal solution is to implement sd_notify() and use Type=notify, or > full blown socket activation should it be appropriate for the daemon. > Both of these cases allow for essentially fire-and-forget style > startup with guarantees of availability for ordering. > > Of course, if you don't think you ever need to order anything on a > given daemon, then Type=simple is just fine. > > HTH, > d I commented a bug about this : https://bugs.archlinux.org/task/31309 Is it safe to assume that if a daemon is meant to be run in foreground (i.e default behaviour, without options) , it is safe to run it this way in the corresponding service file ? -- radio ianux - http://ianux.fr/
[arch-general] gstreamer vs gstreamer0.10
Quick question on the 2 gstreamer packages currently in extra (gstreamer & gstreamer0.10) - is one "preferred" over the other? It looks like gstreamer is v1.0 and is used by gnome3, so is gstreamer0.10 being transitioned out? Do they provide the same functionality? Thanks, Danny G
