[arch-general] Ethernet stopped working after update
My card: # lspci | grep -i ethernet Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03) After doing pacman -Syu, ethernet on my desktop stopped working. The card on my laptop is the same, at least according to lspci, and is working fine. When I upgraded, there was a change in syntax in rc.conf for defining the network, but I'm just attempting dhcp for now before I try to set up a static ip: interface=eth0 address= netmask= gateway= I've tried resetting the router and switching from the kernel's r8169 driver to the r8168 driver from the aur. I compiled the aur driver on my laptop and transferred to the desktop on usb -- as long as they're both x86_64, this shouldn't be a problem, right? Regardless of my choice of driver, ethernet on the laptop works fine, and doesn't work at all on the desktop. If I set up ethernet manually using ifconfig to define the address/netmask/broadcast/etc (making sure the routes are correct), everything appears to work fine until I try to ping the router and get Destination Host Unreachable. And the kicker is that the light on the router for the port I have my ethernet cable plugged into will light up for the laptop, but not the desktop. Given this and the other behavior, I'm inclined to think it's a hardware issue, but this hardware is only several months old, and having this happen right after an upgrade seems unlikely to be a coincidence. Anything else I can try short of reinstalling or getting a replacement from the manufacturer?
Re: [arch-general] Ethernet stopped working after update
On Sun, Jun 26, 2011 at 9:05 PM, dmb...@gmail.com wrote: # lspci | grep -i ethernet Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03) After doing pacman -Syu, ethernet on my desktop stopped working. The card on my laptop is the same, at least according to lspci, and is working fine. When I upgraded, there was a change in syntax in rc.conf for defining the network, but I'm just attempting dhcp for now before I try to set up a static ip: interface=eth0 address= netmask= gateway= Could you try with your old rc.conf? We didn't drop support for the old syntax, so it should still work. It would be good to rule that one out before anything else I think. Secondly, could you possibly downgrade some of your packages to figure out which one caused the problem? My guess is going to be kernel26, initscripts or udev. One more thing: have you noticed the change of syntax in rc.conf for blacklisting modules? Did you blacklist any modules before, that is not getting blacklisted anymore? Could you try blacklisting them using modprobe.conf? Please file a bug report if none of this solves your problem. -t
Re: [arch-general] Ethernet stopped working after update
On Sun, 26 Jun 2011 21:15:15 +0200, Tom Gundersen t...@jklm.no wrote: Change the deamon 'network' to 'networkmanager' solved the problem for me ... On Sun, Jun 26, 2011 at 9:05 PM, dmb...@gmail.com wrote: # lspci | grep -i ethernet Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03) After doing pacman -Syu, ethernet on my desktop stopped working. The card on my laptop is the same, at least according to lspci, and is working fine. When I upgraded, there was a change in syntax in rc.conf for defining the network, but I'm just attempting dhcp for now before I try to set up a static ip: interface=eth0 address= netmask= gateway= Could you try with your old rc.conf? We didn't drop support for the old syntax, so it should still work. It would be good to rule that one out before anything else I think. Secondly, could you possibly downgrade some of your packages to figure out which one caused the problem? My guess is going to be kernel26, initscripts or udev. One more thing: have you noticed the change of syntax in rc.conf for blacklisting modules? Did you blacklist any modules before, that is not getting blacklisted anymore? Could you try blacklisting them using modprobe.conf? Please file a bug report if none of this solves your problem. -t -- Using Opera's revolutionary email client: http://www.opera.com/mail/
Re: [arch-general] Ethernet stopped working after update
On Sun, Jun 26, 2011 at 9:33 PM, Ron van der Nagel rn.mailingli...@gmail.com wrote: Change the deamon 'network' to 'networkmanager' solved the problem for me Just in case this was not clear to everyone: 'networkmanager' (http://projects.gnome.org/NetworkManager/) is completely different from 'network' (our own little script). In particular, they do not share config files, so it is not just as simple as changing the daemon you start, you must also set it up correctly. -t
Re: [arch-general] Ethernet stopped working after update
On Sun, Jun 26, 2011 at 1:05 PM, dmb...@gmail.com wrote: My card: # lspci | grep -i ethernet Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03) After doing pacman -Syu, ethernet on my desktop stopped working. The card on my laptop is the same, at least according to lspci, and is working fine. When I upgraded, there was a change in syntax in rc.conf for defining the network, but I'm just attempting dhcp for now before I try to set up a static ip: interface=eth0 address= netmask= gateway= I've tried resetting the router and switching from the kernel's r8169 driver to the r8168 driver from the aur. I compiled the aur driver on my laptop and transferred to the desktop on usb -- as long as they're both x86_64, this shouldn't be a problem, right? Regardless of my choice of driver, ethernet on the laptop works fine, and doesn't work at all on the desktop. If I set up ethernet manually using ifconfig to define the address/netmask/broadcast/etc (making sure the routes are correct), everything appears to work fine until I try to ping the router and get Destination Host Unreachable. And the kicker is that the light on the router for the port I have my ethernet cable plugged into will light up for the laptop, but not the desktop. Given this and the other behavior, I'm inclined to think it's a hardware issue, but this hardware is only several months old, and having this happen right after an upgrade seems unlikely to be a coincidence. Anything else I can try short of reinstalling or getting a replacement from the manufacturer? I'm using netcfg, and haven't found problems so far with all changes... The daemon is net-profiles, and you can copy the example for static wired profile into a valid profile, and setup rc.conf accordingly. See: https://wiki.archlinux.org/index.php/Netcfg -- Javier.
Re: [arch-general] Ethernet stopped working after update
Some more info: I noticed while looking through pacman.log that this is the first upgrade I've done since 2011-03-26. *wince* On 06/26/2011 02:15 PM, Tom Gundersen wrote: On Sun, Jun 26, 2011 at 9:05 PM,dmb...@gmail.com wrote: # lspci | grep -i ethernet Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03) After doing pacman -Syu, ethernet on my desktop stopped working. The card on my laptop is the same, at least according to lspci, and is working fine. When I upgraded, there was a change in syntax in rc.conf for defining the network, but I'm just attempting dhcp for now before I try to set up a static ip: interface=eth0 address= netmask= gateway= Could you try with your old rc.conf? We didn't drop support for the old syntax, so it should still work. It would be good to rule that one out before anything else I think. Trying dhcp with the old syntax fails, and configuring a static ip appears to succeed, but then fails when I try to do something with the connection. eth0=eth0 192.168.0.116 netmask 255.255.255.0 broadcast 192.168.0.255 INTERFACES=(eth0) gateway=default gw 192.168.0.1 ROUTES=(gateway) Secondly, could you possibly downgrade some of your packages to figure out which one caused the problem? My guess is going to be kernel26, initscripts or udev. After downgrading the kernel, my eth0 device no longer shows up in with ifconfig -a. Downgrading initscripts, udev, and mkinitcpio (which I needed to do for udev) didn't help. Oh, but using r8169 instead of r8168 fixes that. nvm. Still can't get a working connection, though. Any other suggestions for packages to downgrade? One more thing: have you noticed the change of syntax in rc.conf for blacklisting modules? Did you blacklist any modules before, that is not getting blacklisted anymore? Could you try blacklisting them using modprobe.conf? Yes, I noticed this. The only thing I ever blacklisted before the upgrade was pcspkr, and that's no longer loaded automatically. While troubleshooting this issue, I've blacklisted r8169 in /etc/modprobe.d, but I undid that change and uninstalled the r8168 package while downgrading the packages you suggested (see above). Please file a bug report if none of this solves your problem. Should I file it upstream or on Arch's bugtracker? What package/project should I file it with? -t
Re: [arch-general] Ethernet stopped working after update
On Sun, Jun 26, 2011 at 15:17, dmb...@gmail.com wrote: Some more info: I noticed while looking through pacman.log that this is the first upgrade I've done since 2011-03-26. *wince* On 06/26/2011 02:15 PM, Tom Gundersen wrote: On Sun, Jun 26, 2011 at 9:05 PM,dmb...@gmail.com wrote: # lspci | grep -i ethernet Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03) After doing pacman -Syu, ethernet on my desktop stopped working. The card on my laptop is the same, at least according to lspci, and is working fine. When I upgraded, there was a change in syntax in rc.conf for defining the network, but I'm just attempting dhcp for now before I try to set up a static ip: interface=eth0 address= netmask= gateway= Could you try with your old rc.conf? We didn't drop support for the old syntax, so it should still work. It would be good to rule that one out before anything else I think. Trying dhcp with the old syntax fails, and configuring a static ip appears to succeed, but then fails when I try to do something with the connection. eth0=eth0 192.168.0.116 netmask 255.255.255.0 broadcast 192.168.0.255 INTERFACES=(eth0) gateway=default gw 192.168.0.1 ROUTES=(gateway) Secondly, could you possibly downgrade some of your packages to figure out which one caused the problem? My guess is going to be kernel26, initscripts or udev. After downgrading the kernel, my eth0 device no longer shows up in with ifconfig -a. Downgrading initscripts, udev, and mkinitcpio (which I needed to do for udev) didn't help. Oh, but using r8169 instead of r8168 fixes that. nvm. Still can't get a working connection, though. Any other suggestions for packages to downgrade? One more thing: have you noticed the change of syntax in rc.conf for blacklisting modules? Did you blacklist any modules before, that is not getting blacklisted anymore? Could you try blacklisting them using modprobe.conf? Yes, I noticed this. The only thing I ever blacklisted before the upgrade was pcspkr, and that's no longer loaded automatically. While troubleshooting this issue, I've blacklisted r8169 in /etc/modprobe.d, but I undid that change and uninstalled the r8168 package while downgrading the packages you suggested (see above). Please file a bug report if none of this solves your problem. Should I file it upstream or on Arch's bugtracker? What package/project should I file it with? -t I made the following changes to my rc.conf file after the upgrade and haven't had any problems. HOSTNAME=gandalf # interface=eth0 address=192.168.0.5 netmask=255.255.255.0 gateway=192.168.0.1 I haven't tried DHCP. Hope I haven't missed the point and that this helps. Myra -- Life's fun when your sick and psychotic!
Re: [arch-general] Ethernet stopped working after update
dmb...@gmail.com wrote: Trying dhcp with the old syntax fails, and configuring a static ip appears to succeed, but then fails when I try to do something with the connection. eth0=eth0 192.168.0.116 netmask 255.255.255.0 broadcast 192.168.0.255 INTERFACES=(eth0) gateway=default gw 192.168.0.1 ROUTES=(gateway) What does route say in this case? I had a similar problem with the update which was due to the gateway being ignored. At that point I switched to netcfg which worked fine... Jerome -- mailto:jeber...@free.fr http://jeberger.free.fr Jabber: jeber...@jabber.fr signature.asc Description: OpenPGP digital signature
Re: [arch-general] Ethernet stopped working after update
On 06/26/2011 04:53 PM, Jérôme M. Berger wrote: dmb...@gmail.com wrote: Trying dhcp with the old syntax fails, and configuring a static ip appears to succeed, but then fails when I try to do something with the connection. eth0=eth0 192.168.0.116 netmask 255.255.255.0 broadcast 192.168.0.255 INTERFACES=(eth0) gateway=default gw 192.168.0.1 ROUTES=(gateway) What does route say in this case? I had a similar problem with the update which was due to the gateway being ignored. At that point I switched to netcfg which worked fine... Jerome Looks fine to me. Same output as I get on my laptop. # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 192.168.0.1 0.0.0.0 UG0 00 eth0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 00 eth0
Re: [arch-general] Ethernet stopped working after update
On 06/26/2011 02:50 PM, Javier Vasquez wrote:
On Sun, Jun 26, 2011 at 1:05 PM,dmb...@gmail.com wrote:
My card:
# lspci | grep -i ethernet
Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI
Express Gigabit Ethernet controller (rev 03)
After doing pacman -Syu, ethernet on my desktop stopped working. The card on
my laptop is the same, at least according to lspci, and is working fine.
When I upgraded, there was a change in syntax in rc.conf for defining the
network, but I'm just attempting dhcp for now before I try to set up a
static ip:
interface=eth0
address=
netmask=
gateway=
I've tried resetting the router and switching from the kernel's r8169 driver
to the r8168 driver from the aur. I compiled the aur driver on my laptop and
transferred to the desktop on usb -- as long as they're both x86_64, this
shouldn't be a problem, right?
Regardless of my choice of driver, ethernet on the laptop works fine, and
doesn't work at all on the desktop. If I set up ethernet manually using
ifconfig to define the address/netmask/broadcast/etc (making sure the routes
are correct), everything appears to work fine until I try to ping the router
and get Destination Host Unreachable.
And the kicker is that the light on the router for the port I have my
ethernet cable plugged into will light up for the laptop, but not the
desktop. Given this and the other behavior, I'm inclined to think it's a
hardware issue, but this hardware is only several months old, and having
this happen right after an upgrade seems unlikely to be a coincidence.
Anything else I can try short of reinstalling or getting a replacement from
the manufacturer?
I'm using netcfg, and haven't found problems so far with all
changes... The daemon is net-profiles, and you can copy the example
for static wired profile into a valid profile, and setup rc.conf
accordingly.
See:
https://wiki.archlinux.org/index.php/Netcfg
How odd. Every other method I've tried for setting up a static IP
succeeds (but doesn't actually get me a working connection). Netcfg
gives me this:
root@bender:~# cat /etc/network.d/ethernet
CONNECTION='ethernet'
DESCRIPTION='Ethernet'
INTERFACE='eth0'
IP='static'
ADDR='192.168.0.120'
GATEWAY='192.168.0.1'
DNS=('192.168.0.1')
root@bender:~# netcfg ethernet
:: ethernet up
[BUSY]
No connection
[FAIL]
root@bender:~#
Doing 'sh -x netcfg ethernet' shows that it's printing 'No connection'
from '/usr/lib/network/connections/ethernet up ethernet' on this snippet:
if ! checkyesno ${SKIPNOCARRIER:-no} ip link show dev
$INTERFACE | fgrep -q NO-CARRIER; then
sleep ${CARRIER_TIMEOUT:-2} # Some cards are plain slow to come
up. Don't fail immediately.
if ip link show dev $INTERFACE | fgrep -q NO-CARRIER; then
report_iproute No connection
fi
fi
And if I bring up the connection with the old rc.conf syntax, 'ip link
show dev eth0' indeed shows:
2: eth0: NO-CARRIER,BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast
state DOWN qlen 1000
link/ether 00:30:67:8f:7c:a8 brd ff:ff:ff:ff:ff:ff
Which maybe means something to someone. ;)
At this point, I'm ready to chalk it up to the hardware. I can reboot my
laptop, and the light on the router that indicates that it sees the
ethernet cable will only turn off for a second here and there throughout
the shutdown/boot process. I do the same with this machine, and don't
see so much as a flicker. I tried downloading and booting from an ubuntu
live cd and didn't have any luck getting a connection. And both of my
machines are using the same NIC (at least according to lspci), and
should be at roughly the same version of the applicable software -- I
updated my laptop an hour, at most, before I updated my desktop.
Re: [arch-general] Ethernet stopped working after update
Excerpts from dmbuce's message of 2011-06-27 01:03:06 +0200:
On 06/26/2011 02:50 PM, Javier Vasquez wrote:
On Sun, Jun 26, 2011 at 1:05 PM,dmb...@gmail.com wrote:
My card:
# lspci | grep -i ethernet
Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI
Express Gigabit Ethernet controller (rev 03)
After doing pacman -Syu, ethernet on my desktop stopped working. The card
on
my laptop is the same, at least according to lspci, and is working fine.
When I upgraded, there was a change in syntax in rc.conf for defining the
network, but I'm just attempting dhcp for now before I try to set up a
static ip:
interface=eth0
address=
netmask=
gateway=
I've tried resetting the router and switching from the kernel's r8169
driver
to the r8168 driver from the aur. I compiled the aur driver on my laptop
and
transferred to the desktop on usb -- as long as they're both x86_64, this
shouldn't be a problem, right?
Regardless of my choice of driver, ethernet on the laptop works fine, and
doesn't work at all on the desktop. If I set up ethernet manually using
ifconfig to define the address/netmask/broadcast/etc (making sure the
routes
are correct), everything appears to work fine until I try to ping the
router
and get Destination Host Unreachable.
And the kicker is that the light on the router for the port I have my
ethernet cable plugged into will light up for the laptop, but not the
desktop. Given this and the other behavior, I'm inclined to think it's a
hardware issue, but this hardware is only several months old, and having
this happen right after an upgrade seems unlikely to be a coincidence.
Anything else I can try short of reinstalling or getting a replacement from
the manufacturer?
I'm using netcfg, and haven't found problems so far with all
changes... The daemon is net-profiles, and you can copy the example
for static wired profile into a valid profile, and setup rc.conf
accordingly.
See:
https://wiki.archlinux.org/index.php/Netcfg
How odd. Every other method I've tried for setting up a static IP
succeeds (but doesn't actually get me a working connection). Netcfg
gives me this:
root@bender:~# cat /etc/network.d/ethernet
CONNECTION='ethernet'
DESCRIPTION='Ethernet'
INTERFACE='eth0'
IP='static'
ADDR='192.168.0.120'
GATEWAY='192.168.0.1'
DNS=('192.168.0.1')
root@bender:~# netcfg ethernet
:: ethernet up
[BUSY]
No connection
[FAIL]
root@bender:~#
Doing 'sh -x netcfg ethernet' shows that it's printing 'No connection'
from '/usr/lib/network/connections/ethernet up ethernet' on this snippet:
if ! checkyesno ${SKIPNOCARRIER:-no} ip link show dev
$INTERFACE | fgrep -q NO-CARRIER; then
sleep ${CARRIER_TIMEOUT:-2} # Some cards are plain slow to come
up. Don't fail immediately.
if ip link show dev $INTERFACE | fgrep -q NO-CARRIER; then
report_iproute No connection
fi
fi
And if I bring up the connection with the old rc.conf syntax, 'ip link
show dev eth0' indeed shows:
2: eth0: NO-CARRIER,BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast
state DOWN qlen 1000
link/ether 00:30:67:8f:7c:a8 brd ff:ff:ff:ff:ff:ff
Which maybe means something to someone. ;)
At this point, I'm ready to chalk it up to the hardware. I can reboot my
laptop, and the light on the router that indicates that it sees the
ethernet cable will only turn off for a second here and there throughout
the shutdown/boot process. I do the same with this machine, and don't
see so much as a flicker. I tried downloading and booting from an ubuntu
live cd and didn't have any luck getting a connection. And both of my
machines are using the same NIC (at least according to lspci), and
should be at roughly the same version of the applicable software -- I
updated my laptop an hour, at most, before I updated my desktop.
Did you try running dhcpcd manually after boot? I'm new to netcfg and
thought it's normal behavior that I have to launch dhcpcd afterwards..
Re: [arch-general] Ethernet stopped working after update
On 06/26/2011 06:17 PM, Philipp Überbacher wrote:
Excerpts from dmbuce's message of 2011-06-27 01:03:06 +0200:
On 06/26/2011 02:50 PM, Javier Vasquez wrote:
On Sun, Jun 26, 2011 at 1:05 PM,dmb...@gmail.com wrote:
My card:
# lspci | grep -i ethernet
Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI
Express Gigabit Ethernet controller (rev 03)
After doing pacman -Syu, ethernet on my desktop stopped working. The card on
my laptop is the same, at least according to lspci, and is working fine.
When I upgraded, there was a change in syntax in rc.conf for defining the
network, but I'm just attempting dhcp for now before I try to set up a
static ip:
interface=eth0
address=
netmask=
gateway=
I've tried resetting the router and switching from the kernel's r8169 driver
to the r8168 driver from the aur. I compiled the aur driver on my laptop and
transferred to the desktop on usb -- as long as they're both x86_64, this
shouldn't be a problem, right?
Regardless of my choice of driver, ethernet on the laptop works fine, and
doesn't work at all on the desktop. If I set up ethernet manually using
ifconfig to define the address/netmask/broadcast/etc (making sure the routes
are correct), everything appears to work fine until I try to ping the router
and get Destination Host Unreachable.
And the kicker is that the light on the router for the port I have my
ethernet cable plugged into will light up for the laptop, but not the
desktop. Given this and the other behavior, I'm inclined to think it's a
hardware issue, but this hardware is only several months old, and having
this happen right after an upgrade seems unlikely to be a coincidence.
Anything else I can try short of reinstalling or getting a replacement from
the manufacturer?
I'm using netcfg, and haven't found problems so far with all
changes... The daemon is net-profiles, and you can copy the example
for static wired profile into a valid profile, and setup rc.conf
accordingly.
See:
https://wiki.archlinux.org/index.php/Netcfg
How odd. Every other method I've tried for setting up a static IP
succeeds (but doesn't actually get me a working connection). Netcfg
gives me this:
root@bender:~# cat /etc/network.d/ethernet
CONNECTION='ethernet'
DESCRIPTION='Ethernet'
INTERFACE='eth0'
IP='static'
ADDR='192.168.0.120'
GATEWAY='192.168.0.1'
DNS=('192.168.0.1')
root@bender:~# netcfg ethernet
:: ethernet up
[BUSY]
No connection
[FAIL]
root@bender:~#
Doing 'sh -x netcfg ethernet' shows that it's printing 'No connection'
from '/usr/lib/network/connections/ethernet up ethernet' on this snippet:
if ! checkyesno ${SKIPNOCARRIER:-no} ip link show dev
$INTERFACE | fgrep -q NO-CARRIER; then
sleep ${CARRIER_TIMEOUT:-2} # Some cards are plain slow to come
up. Don't fail immediately.
if ip link show dev $INTERFACE | fgrep -q NO-CARRIER; then
report_iproute No connection
fi
fi
And if I bring up the connection with the old rc.conf syntax, 'ip link
show dev eth0' indeed shows:
2: eth0:NO-CARRIER,BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast
state DOWN qlen 1000
link/ether 00:30:67:8f:7c:a8 brd ff:ff:ff:ff:ff:ff
Which maybe means something to someone. ;)
At this point, I'm ready to chalk it up to the hardware. I can reboot my
laptop, and the light on the router that indicates that it sees the
ethernet cable will only turn off for a second here and there throughout
the shutdown/boot process. I do the same with this machine, and don't
see so much as a flicker. I tried downloading and booting from an ubuntu
live cd and didn't have any luck getting a connection. And both of my
machines are using the same NIC (at least according to lspci), and
should be at roughly the same version of the applicable software -- I
updated my laptop an hour, at most, before I updated my desktop.
Did you try running dhcpcd manually after boot? I'm new to netcfg and
thought it's normal behavior that I have to launch dhcpcd afterwards..
Well, I was trying to set up a static connection, so dhcpcd shouldn't be
needed. But I've set up dhcp connections before with netcfg that launch
dhcpcd connections automatically. Maybe you could post your config (in a
new thread, preferably, so as not to hijack this one).
Re: [arch-general] Ethernet stopped working after update
2: eth0: NO-CARRIER,BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast state DOWN qlen 1000 link/ether 00:30:67:8f:7c:a8 brd ff:ff:ff:ff:ff:ff Which maybe means something to someone. ;) NO-CARRIER,,UP means it's configured to be up, but it doesn't sense an ethernet connectivity. Check the cables, and the kernel driver. -- дамјан
[arch-general] Makepkg. Disabling automatically aborting on any errors during packaging
Hello. As you know makepkg since 3.4.0 has feature automatically aborting on any errors during packaging. Sometimes this feature makes me cry, for example, if build() function has: rm [non-existent file] 2 /dev/null This problem is not critical if you are author of the build()'s code (you can adapt code for the capricious makepkg). But i encountered the following situation: i maintain psi-plus aur package. This project has bash library libpsibuild.sh for making (because it is a complex process). I use this library in the build() function of the PKGBUILD. If i run build() function just under the bash, program builds great, but with makepkg it falls with error. I can do patch for this library, but it is not good solution, because of this library updates literally every day. So i requesting something like boolean variable in the PKGBUILD, which can switch automatically aborting. If author preferred to disable this feature, he will take care of error handling in the code directly. As i know, gentoo portages has somesing like this.
Re: [arch-general] Makepkg. Disabling automatically aborting on any errors during packaging
On 27/06/11 13:15, Joker-jar wrote: Hello. As you know makepkg since 3.4.0 has feature automatically aborting on any errors during packaging. Sometimes this feature makes me cry, for example, if build() function has: rm [non-existent file] 2 /dev/null This problem is not critical if you are author of the build()'s code (you can adapt code for the capricious makepkg). But i encountered the following situation: i maintain psi-plus aur package. This project has bash library libpsibuild.sh for making (because it is a complex process). I use this library in the build() function of the PKGBUILD. If i run build() function just under the bash, program builds great, but with makepkg it falls with error. I can do patch for this library, but it is not good solution, because of this library updates literally every day. So i requesting something like boolean variable in the PKGBUILD, which can switch automatically aborting. If author preferred to disable this feature, he will take care of error handling in the code directly. As i know, gentoo portages has somesing like this. Not going to happen. Use: libpsibuild.sh || true and the error in libpsibuild.sh will be ignored. Allan
Re: [arch-general] Makepkg. Disabling automatically aborting on any errors during packaging
i use libpsibuild.sh so: . ./libpsibuild.sh function_from_libpsibuild other_function_from_libpsibuild so, i can do: function_from_libpsibuild || true other_function_from_libpsibuild || true and it will be work fine?
Re: [arch-general] Makepkg. Disabling automatically aborting on any errors during packaging
On 27/06/11 13:56, Joker-jar wrote: i use libpsibuild.sh so: . ./libpsibuild.sh function_from_libpsibuild other_function_from_libpsibuild so, i can do: function_from_libpsibuild || true other_function_from_libpsibuild || true and it will be work fine? If you define fine as ignoring any error in those functions, then yes...
